Roles and permissions
A role is a set of permissions: what someone may see and do in the portal. Each person gets one or more roles in each workspace they belong to.
How roles work
- Roles are defined once for the whole account and given per workspace. The same person can be an editor in one workspace and a super admin in another.
- A person can do what any of their roles allows in the workspace they're working in.
- Super admin holds every permission, including new ones as features are added. It can't be edited or deleted.
- Roles are managed under Settings → Roles. Only a super admin can create, edit or delete a role. Giving roles to people is done on Users and on a workspace's Users tab, by a super admin or someone whose role allows assigning roles.
Permissions
For each kind of record (Branded Pages, links, themes, Brand Vault assets and so on) the role editor lists the same actions:
| Permission | Allows |
|---|---|
| View Any / View | Seeing the list and opening a record |
| Create | Creating one (also limited by your plan) |
| Update | Editing it |
| Replicate | Making a copy |
| Delete / Delete Any | Moving it to the trash |
| Restore / Restore Any | Bringing it back from the trash |
| Force Delete / Force Delete Any | Removing it from the trash for good |
| Reorder | Changing its position in lists that can be ordered |
Some features add permissions of their own, beyond those actions:
| Permission | Allows | Page |
|---|---|---|
| View Billing | Opening Plan & usage | Plan and usage |
| Manage Billing | Reserved for self-serve plan changes | Plan and usage |
| View Embed Policy | Opening Embeds and scripts, read-only | Embeds and scripts |
| Manage Embed Policy | Changing what the account's pages may embed and whether scripts run, for every workspace | Embeds and scripts |
| Update Custom Css | Writing custom CSS on themes, on top of editing the theme | Custom CSS |
| Create Api Tokens | Creating personal API tokens | API tokens |
| Creating share links | Share links and email invitations on private pages | Share links |
| Design system permissions (import, publish, share links) | Bringing in versions, making one current or the default, sharing as a skill | Design systems |
| Team cards permissions (import, custom fields, review changes, customize a card) | Importing people, managing custom fields, approving change requests, changing one person's card | People |
A record shared with your workspace from another one stays read-only, whatever your role allows.
Good to know
- Claude and the API never go beyond the role. A Claude connection or an API token acts as the person who created it, with that person's roles in that workspace.
- Removing a permission applies at once, on the person's next action.
- Super admin accounts are protected: only another super admin can edit, suspend or delete them.
With Claude
Claude can't manage roles or permissions yet: that stays in the panel. Everything Claude does through the Claude connector is limited by the role of the person who connected it.