Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Mason McCoy
Beigetreten 15. Apr. 2021
·
Letzte Aktivität 22. Feb. 2024
Folge ich
0
Follower
0
Gesamtaktivitäten
31
Stimmen
11
Abonnements
18
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Mason McCoy
Mason McCoy hat einen Kommentar hinterlassen
Ditto to Marks' comment, we'll also need to be able to report on these fields in Explore.
Kommentar anzeigen · Gepostet 08. Nov. 2022 · Mason McCoy
0
Follower
0
Stimmen
0
Kommentare
Mason McCoy hat einen Post erstellt
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.
Gepostet 16. März 2021 · Mason McCoy
0
Follower
5
Stimmen
2
Kommentare