Recherches récentes
Pas de recherche récente

Mason McCoy
Adhésion le 15 avr. 2021
·
Dernière activité le 22 févr. 2024
Suivis
0
Abonnés
0
Activité totale
31
Votes
11
Abonnements
18
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Mason McCoy
Mason McCoy a ajouté un commentaire,
Ditto to Marks' comment, we'll also need to be able to report on these fields in Explore.
Afficher le commentaire · Publication le 08 nov. 2022 · Mason McCoy
0
Abonnés
0
Votes
0
Commentaire
Mason McCoy a créé une publication,
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.
Publication le 16 mars 2021 · Mason McCoy
0
Abonnés
5
Votes
2
Commentaires