Plan requirement
| Subscription | Any plan |
| Access | Admin |
Changing what somebody can do. Quick, and worth checking what it changed afterwards.
Change it
- Open the team member in Admin Center.
- Change the role.
- Check their ticket access, which may not have followed.
- Check their group membership.
- Tell them what changed.
Role and access are separate
Changing the role does not necessarily change which tickets they can open. Somebody moved to a narrower role can keep access to everything, which is exactly the case you were trying to close.
Check both, every time.
Promoting to admin
Costs nothing extra and grants the ability to change configuration for everybody. Worth a conversation about what you expect them to change, and what they should ask about first.
Reducing a role
Somebody moving to another team, or stepping back from support. Reduce it the day the change happens, not when somebody remembers.
Access that outlives the reason for it is the most common finding in any access review.
Their work stays with them
Tickets, comments and history follow the person regardless of role changes. Nothing is lost by adjusting it.
Tell them
Somebody who suddenly cannot do what they could yesterday will report it as a fault. One message prevents that, and it prevents them asking a colleague to do it instead.
Comments
0 comments
Article is closed for comments.