Collaboration
Roles & Permissions
This page has been cleared and is ready for updated Builder Studio documentation.
Permissions in BuilderStudio are assigned per workspace. Every member has exactly one effective role, and that role decides what they can do across every canvas and credential the workspace owns. There are four roles: owner, admin, editor, and viewer.
Two privilege axes
Roles gate two different kinds of action: canvas work (editing nodes, edges, media, and canvas settings) and workspace administration (renaming the workspace, managing members and invites, deleting canvases, billing). A role can allow one without the other — a viewer has neither, an editor has canvas work only, and admins/owner have both.
The roles
- Owner — the single creator of the workspace, stored on the workspace itself rather than as a member row. The owner has full control and is immutable: ownership cannot be changed through the membership tools, and the owner cannot be removed or have their role edited.
- Admin — full canvas work plus workspace administration. Admins can manage members and invites, but with one carve-out around other admins (below).
- Editor — can do canvas work (create and edit canvases, nodes, edges, and media) but cannot administer the workspace or its membership.
- Viewer— read access to the workspace and its canvases, with no editing and no administration. This is also the fail-closed default: if a member's role can't be resolved cleanly, they are treated as a viewer rather than granted more.
Capability matrix
| Capability | Owner | Admin | Editor | Viewer |
|---|---|---|---|---|
| View the workspace and its canvases | Yes | Yes | Yes | Yes |
| Edit canvases (nodes, edges, media, canvas settings) | Yes | Yes | Yes | No |
| Delete canvases and manage invites | Yes | Yes | No | No |
| Rename workspace, manage members | Yes | Yes | No | No |
| Invite or manage admins | Yes | No | No | No |
| Delete the workspace | Yes | No | No | No |
Owner-only over admins
Admins can administer the workspace, but they cannot escalate other people to admin or touch existing admins. Specifically, only the owner can invite someone as an admin, change a member's role to or from admin, or remove an admin. This keeps the admin tier under the owner's sole control while still letting admins manage editors and viewers.
How it's enforced
The role checks are not advisory UI state — they run on the server for every request. BuilderStudio resolves your role on the target workspace, then gates the action against it. Canvas work requires owner, admin, or editor; workspace administration requires owner or admin; admin-tier changes require owner.
Role gatestext
view -> owner | admin | editor | vieweredit a canvas -> owner | admin | editoradmin a workspace-> owner | adminmanage admins -> owner onlydelete workspace -> owner onlyLeast-privilege on conflicts
If duplicate membership records ever exist for the same person in one workspace, the system resolves them to the least privileged role rather than the highest. Roles never silently widen.
Related
- Inviting Members — choosing a role when you invite someone and changing it later.
- Workspaces — what a role grants access to.
Was this page helpful?