Recent searches
No recent searches

Mason McCoy
Joined Apr 15, 2021
·
Last activity Feb 22, 2024
Following
0
Followers
0
Total activity
31
Votes
11
Subscriptions
18
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Mason McCoy
Mason McCoy commented,
Ditto to Marks' comment, we'll also need to be able to report on these fields in Explore.
View comment · Posted Nov 08, 2022 · Mason McCoy
0
Followers
0
Votes
0
Comments
Mason McCoy created a post,
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.
Posted Mar 16, 2021 · Mason McCoy
0
Followers
5
Votes
2
Comments