Admin roles and what each can do
Summary
Section titled “Summary”Authorization is enforced on the server. With a simplified Clerk setup, Admin (org:admin) maps to full access and Member (org:member) maps to Editor.
| Capability | Owner | Admin | Editor | Viewer | Billing Admin |
|---|---|---|---|---|---|
| View admin | Yes | Yes | Yes | Yes | Yes |
| Incidents / maintenance / global alerts | Yes | Yes | Yes | No | No |
| Pages / services catalog | Yes | Yes | No | No | No |
| Branding / languages / system / subscribers | Yes | Yes | No | No | No |
| Billing | Yes | Yes | No | No | Yes |
| Delete workspace | Yes | Yes* | No | No | No |
* Code allows Owner or Admin for workspace destruction (canDestroyWorkspace); UI copy for deletion emphasizes Owner.
Prerequisites
Section titled “Prerequisites”None — concept article. Manage assignments in the Clerk organization menu.
- Open the organization menu in the admin header.
- Assign Clerk roles that map to the capabilities you need.
[Screenshot: Dashboard Members card hint about organization menu]
Result
Section titled “Result”Teammates only see and can change what their role allows.
Related articles
Section titled “Related articles”Sources (for verification)
Section titled “Sources (for verification)”src/server/rbac.tssrc/lib/clerk-org-roles.tsmessages/en.json → admin.accessmessages/en.json → admin.workspaceDeletion