We have had a user cause a lot of "noise" by managing to send a large amount of emails to our internal team - all due to not following our usual process and getting himself caught up in a workflow he should not have been using.
The user received a transmittal and the saw there was an option to "Start responding" as per the highlight on the attached screenshot, so he clicked it then got himself in all sorts of difficulties and managed to unintentionally raise a design issue, send it to a role based group, the recipients then responded and huge numbers of emails were sent, sent again when the recipients responded and so on....
My idea is that this "Start responding" option should be made a role based (or generally configurable) so that based upon user permission/role this can be hidden / not available or is "greyed out" so that it cannot be clicked.
|
Practical use of functionality?
To stop people who we don't want to start involving the wrong people doing so! |
|
|
What is the impact of not doing this?
This will be clicked again by a user, and if they then assign to a large group (as in my example to a role based group) then large numbers of users get involved, a lot of time is wasted and our doc controller is swamped with requests and complaints. |