Workspace roles
Every workspace member has one of six roles.Workspace-scoped permissions
✅ means the role has the permission. ❌ means it does not.judges.view and judges.manage gate Intelligent Authorization. Preconfigured judges remain immutable regardless of judges.manage. Renamed from moot.view / moot.manage in the 2026-06 release.
eventing.* gates Subscribe to Events. filters.* gates Guard filter configuration. See those how-tos for operation detail.
workspace.manage_admin is the workspace-direct admin marker. It gates adding, removing, or changing the role of any user to or from workspace admin. It distinguishes workspace admin from workspace operator. The latter operates the workspace end-to-end but cannot reshape its admin roster. The distinction collapses at the tenant scope. Tenant admin and tenant operator cascades both grant workspace.manage_admin across every workspace in the tenant. Org owner and admin cascades grant it as well.
Tenant roles
Tenant roles grant tenant-scoped permissions and cascade workspace permissions into every workspace in the tenant.Tenant-scoped permissions
✅ means the role has the permission. ❌ means it does not.
Tenant admin, operator, and security inherit workspace permissions across every workspace in the tenant. Tenant member receives no workspace cascade. Assign a workspace role separately to grant workspace access.
tenant.delete is the admin-only marker at the tenant-direct scope, analogous to workspace.delete. Tenant operators run the tenant end-to-end but cannot delete it. Org owner and admin cascade tenant.delete across every tenant.
Organization roles
Organization roles cascade into every tenant and workspace in the org.Org-scoped permissions
✅ means the role has the permission. ❌ means it does not.org.view gates “I’m a real participant in this org” reads. The ListJoinableTenants endpoint requires it, so unprivileged invitees cannot enumerate the org’s open tenants.
Grantable permission discovery
Platform API keys take an explicit permission list. Discover what the caller may grant with:- CLI:
dome platform-keys permissions - MCP:
dome_platform_keys_available_permissions - API:
GetGrantablePermissions,ResolvePermissions
Next steps
Grant these from Manage Access. Agent runtime auth is Cedar:- Permissions concept for how platform RBAC relates to agent authorization
- Manage Access to assign members and create platform keys
- Scopes concept for the org → tenant → workspace hierarchy
- Authorization Model concept for Cedar agent authorization
- Rules reference for the entity, action, and attribute catalogs