Allow Agents (Staff) to Edit Organization(s) on their own Profile
Our current use case requires that only the Team Leader role has the permission to "add or modify groups & organizations" because these have a high impact on our ticket routing.
The Staff role has the permission to "Add, edit, and delete for all end users" but they do NOT have the "Can add or modify groups & organizations" permission.
Staff are able to update End User profiles to associate them with Organizations, which works as expected.
The problem is that they cannot update organizations on their own personal profile.
Our use case means Staff need to be associated with customer organizations in some cases, but only the Team Leader role can edit the organization on Staff user profiles.
This seems counterintuitive since Staff can edit the organization on an End User profile, but not on their own profile.
Please allow Staff to edit the organization on their own profile under the current permissions or make a change to the permissions structure that allows them to do so.
The current setup creates a bottleneck where Staff organization updates are bottlenecked with our Team Leaders.
-
Our use case would be different, but I agree that a re-thinking of permissions/access to Organizations and End Users needs to be done for various agents and groups; we, too, have a bottleneck around this situation, and I think it could be improved by something like adding read/modify/full access rights to such things from a top-down/tree-level perspective.
-
This is more than a year old, but I just discovered that agents (staff) are unable to update the organization(s) that they belong to, so I'll throw in my vote for this as well.
Vous devez vous connecter pour laisser un commentaire.
2 Commentaires