Skip to main content

Assignments — /rbac/assignments

The Assignments page is where you manage what a role contains and who carries it. The page is role-centric: pick a role from the left panel, then use the two tabs on the right to manage its Members (the actors assigned to it) and its Permissions (the per-resource-type defaults that the role grants).

What you see​

Role picker​

A searchable list of every role in the workspace down the left side. Pick one to load its members and default-permission set on the right. The selected role's system/custom flag and member counts are shown alongside the name.

Members tab​

A table (cards on mobile) with one row per actor assignment:

  • Actor — actor ID and type (USER, BOT, INTEGRATION, DELEGATED_AGENT)
  • Scope — workspace-wide, or scoped to a specific resource type + resource ID (entity scope)
  • Granted at — when the assignment was created

Assignments take effect immediately when created; the underlying contract does not define an approval/pending state.

Permissions tab​

The list of default permissions attached to this role — one row per resourceType × level combination. This is what the evaluator consults at Step 6 ("Role default permission"). Each row shows:

  • Resource type (e.g. project, file)
  • Level (VIEWER, EDITOR, ADMIN) — the role's grant tier on that resource type
  • Granted at

Adding a row tells RBAC "actors with this role default to level X on resource type Y". Per-action RolePermissionOverride rows (Step 5) are a separate, finer-grained mechanism and are not edited from this tab.

Things you can do​

TaskHowPermission
Pick a role to manageTap the role in the left panelread access to RBAC
Filter members or permissionsUse the search box above the active tabread access to RBAC
Add a member+ Assign member in the Members tabassignment:create
Remove a memberTrash icon on the row, confirmassignment:delete
Add a default permission+ Add permission in the Permissions tabrole:update
Remove a default permissionTrash icon on the row, confirmrole:update
Jump to the role detailHeader link on the selected roleread access to RBAC

To change scope or expiry of an existing member assignment, revoke and re-create it. The contract exposes assignRoleToActor, removeRoleFromActor, and bulkAssignRole; modifying an existing assignment row in place is not supported (see modules/rbac/specs/03-graphql-contract.md).

Adding a member​

+ Assign member opens a dialog that asks for:

  1. Actor ID — paste the user / bot / integration / delegated-agent identifier.
  2. Actor type — one of USER, BOT, INTEGRATION, DELEGATED_AGENT.
  3. Entity scope (optional) — tick Scope to a resource to enter a resource type and resource ID; otherwise the assignment is workspace-wide.

Tap Assign. The new row appears in the Members table and the actor sees the new permissions on their next request.

Bulk membership for the same role across many actors is supported by the backend (bulkAssignRole) but is driven from the API / CLI today, not from this UI.

Removing a member​

Tap the trash icon, confirm the dialog. The actor loses any permissions that role granted (other roles they hold are unaffected). The action is recorded in the audit feed and on the actor's profile.

If you revoke your own assignment to a powerful role, double-check that another administrator can still access the workspace before confirming.

Adding a default permission​

+ Add permission in the Permissions tab opens a dialog that asks for:

  1. Resource type — pick from the workspace's registered resource types (sourced from resourceTypes). Already-assigned resource types are filtered out to prevent duplicates.
  2. Level — VIEWER, EDITOR, or ADMIN. This maps onto the viewerDefault / editorDefault / adminDefault flags of each action definition for that resource type — see Resources.

Save. Every actor that currently holds this role inherits the new default on their next permission check.

Pagination​

Each tab is paginated independently. Choose page size (25 / 50 / 100) from the dropdown.

Tips​

  • The Members tab is the fastest place to revoke or re-scope a single user's grant of a specific role. For a per-actor cross-role view, use the Agents page instead.
  • The Permissions tab is the right place to change what the role can do by default. For per-action overrides (single-permission grants or denials that don't fit the Viewer/Editor/Admin tiers), use the role's override surface in Role Detail — backed by the createRolePermissionOverride mutation.
  • Assignments take effect immediately; there is no approval queue. If a teammate says "I got an email but I can't do X yet", verify the role actually grants the permission they expect (use the Permission Checker).
  • The platform does not prune removed assignment rows on its own — they are retained for as long as the operator's database retention policy allows. Any retention window is a property of your workspace's audit/data-retention configuration, not of this UI.