Role Detail — /rbac/roles/:roleId
The Role Detail page is where you inspect everything about a single role: the permissions it carries, who has it, the tags on it, and the recent change history. To make bulk changes to who holds the role or what default permissions the role grants, use the role-centric Assignments page; to edit the role's name/description/parent/permissions in one shot, use Edit (which opens /rbac/roles/:roleId/edit).
What you see
Header
- Role name and a colored badge for type (
system/custom) - Description (if set)
- Tags — chips showing each tag attached to the role
- Action buttons (top-right) — Edit, Duplicate, Delete — visible when you have the matching permission and the role is not a system role (system roles are immutable; only Duplicate is offered)
Tabs
The page is organized into tabs. Tap a tab to switch.
1. Permissions
The permissions this role grants, grouped by resource. Each row shows:
- The permission key (e.g.
project:read) - A short description
- Whether the permission is default-on for this role or has been explicitly granted / denied via override
Use the search box to find a permission quickly inside a role with many entries.
2. Members
Actors currently assigned this role:
- Name / identifier
- Actor type — one of
USER,BOT,INTEGRATION,DELEGATED_AGENT(orGROUPfor group-scoped assignments) - Scope — which workspace or resource the assignment applies to
- Granted at — when the assignment was created
Tap a member row to view that actor's full assignment list.
3. Activity
Change log for this role:
- Created, updated, permissions changed, members added/removed
- Each row shows actor, timestamp, and a short summary
- Newest first
4. Tags
Tags attached to the role (read-only in this surface):
- Existing tags shown as chips for quick visual classification
- The chips reflect what is already attached; this page does not let you attach or remove tags
- Tag attach/detach for roles is handled in the workspace Tags admin surface; if the role needs different tags, manage them there
Note: a future iteration may surface tag attach/detach inline here. Today this tab is read-only by design (
RbacTagChips+getEntityTags).
Things you can do
| Task | Where | Permission |
|---|---|---|
| View permissions | Permissions tab | read access to RBAC |
| View members | Members tab | read access to RBAC |
| View activity | Activity tab | read access to RBAC |
| Edit name / description / permissions | Edit button | role:update |
| Duplicate the role | Duplicate button | role:create |
| Delete the role | Delete button | role:delete |
| Add a tag | Tags tab → + Add tag | role:update (handled via the tags service) |
| Remove a tag | Tags tab → tap × on chip | role:update (handled via the tags service) |
System roles
System roles have a few extra restrictions enforced by the backend:
- They cannot be deleted.
- They cannot be modified —
updateRolerejects changes to system roles (seemodules/rbac/specs/03-graphql-contract.md, Role CRUD). The Edit button is hidden for system roles, and any attempt to mutate them via the API returns an error. - To adjust a system role's permissions, use Duplicate to create an editable custom role from it.
Empty states
- If no actors are assigned, the Members tab shows a "no members yet" card with an Assign role button (admins only).
- If no activity is recorded, the Activity tab shows a quiet "no recent activity" message.
Pagination
The Members and Activity tabs are paginated. Long lists load in pages of 25, with Older / Newer buttons in the footer.
Tips
- The fastest way to find out why an actor has a certain permission is to open the role here and check the Permissions tab — if the permission is listed and not denied, the role is the source.
- For a per-actor view (with all of their roles combined), use the Permission Checker instead.
- Duplicating a role is a safe way to experiment — change the copy, then assign it to one user before rolling it out widely.