How to delete a role
Permanently remove a custom role from the workspace. Work out who holds it first as deleting a role removes its access from every one of them at once.
Before you begin
You need the Account Admin role and the name of the role.
Find out who holds the role before you delete it. A role can be assigned directly to users and to groups, and deleting it removes that access everywhere at once. Check both:
- User Management — users with the role assigned directly
- Group Management — groups carrying the role, which reaches every member and every subgroup below them
If you’re not certain, edit the role down to nothing instead of deleting it. Unchecking its permissions makes it harmless while keeping the record, and lets you restore it if you were wrong. An unused role costs nothing to leave in place.
Steps
Step 1. Check who holds it
Do this before anything else. Search User Management for direct assignments and Group Management for groups carrying the role. Anyone on either list loses this access when the role goes.
Step 2. Reassign anyone who still needs the access
Give them an alternative role first. Doing it in this order means nobody loses access even briefly.
Step 3. Open Roles Management
From the main navigation, click Admin, then open the Roles Management tab.
Step 4. Find the role
Search for it by name and check it’s the right one. Role names can look alike, and there’s no undo.
Step 5. Delete
Click the delete icon in the role’s Settings column, then click Ok at the warning prompt.
Result
The role is gone from Roles Management. Anyone who held it either directly or through a group no longer has the access it granted, unless another role still grants the same thing.
Nothing that was created under the role is affected. Reports, pipelines, and rules stay in the workspace; only the access to reach them changes.
Common issues
- I deleted the wrong role. It can’t be recovered. Recreate it with the same configuration and reassign it to the users and groups that held it. Access is restored, but the creation history isn’t.
- Users lost more access than expected. The role was granting something you hadn’t accounted for, or it was attached to a group whose subgroups you didn’t check. Group-attached roles reach further than group-attached users.
- Users lost nothing at all. Another role or group grants the same access. That’s normal, and it means the role was redundant.