Role Hierarchy — /rbac/roles/hierarchy
The Role Hierarchy page is a read-only tree visualization of every role in the workspace, grouped by its parent link. It is the easiest way to see at a glance how custom roles are organized relative to system roles.
What you see
A back link to Roles in the header, then an indented tree of roles. Each node is a card showing:
- The role name
- A
Systemchip when the role is built-in - The optional description
- Priority (lower is higher-precedence at evaluator Step 6)
- Child role count — how many roles list this role as their parent
Children are indented under their parent. Roles without a parent (or whose parent is missing from the workspace) are rendered as root nodes; the roots are sorted by ascending priority, then by name.
Things you can do
| Task | How | Permission |
|---|---|---|
| Open the hierarchy view | Roles → View hierarchy, or /rbac/roles/hierarchy | canViewRoles |
| Open a role from the tree | Currently not interactive — return to Roles | n/a |
The page itself does not expose mutations. Re-parenting is done from the role's Edit form via the parentRoleId field; see Role Detail and Roles.
Permissions you need
canViewRoles (rbac:read / module-rbac:role:read; admins bypass). The hierarchy reuses the same useRolesWithHierarchy data source that powers the Roles list — there is no separate permission for it.
How "parent" is used by the evaluator
The parent link is metadata only in the current contract — see the note on Roles. A child role does not inherit permissions from its parent. The hierarchy view exists to help admins organize roles visually and discover relationships; it does not change the 8-step evaluator behavior.
If your workspace actually wants permission inheritance, model it as additional role assignments (an actor holds both the parent and the child role) rather than relying on the parent link.
Tips
- A role whose parent has been deleted (or whose parent lives outside the current workspace scope) appears as a root in the tree — there is no broken-link indicator.
- Priority sorting is ascending: a role with
priority: 10renders above one withpriority: 100. Step 6 of the evaluator picks the lowest priority value first, so the tree reflects evaluator order. - For a flat, filterable browse of every role (with member counts and update timestamps), use Roles instead.