Team members
Add Studio editors and viewers as the owner. Check who can edit code, use AI, publish pages and manage settings.
As the site owner, add an account for each person who needs Studio access. Editors can change code, use AI and publish; viewers have read-only access.
Roles
| Role | Access |
|---|---|
| Owner | Full access. Manages team, settings, AI configuration, publishing, and all content. One owner per installation. |
| Editor | Can edit pages, manage assets, use the AI chat, use notes, use the board, work with forms, manage designs, and publish. Cannot access Settings or Team management. |
| Viewer | Read-only access. Can view the site preview, pages, and assets. Cannot make any changes. |
Adding team members
- Open the Team page from your account dropdown (top-right)
- Click Add Member
- Enter their name, email, and a temporary password
- Select a role (Editor or Viewer)
- Share the credentials - they can change their password after signing in
No email configuration is required. Share credentials through a private channel. Team changes use retained operations with current-account checks; a stale record or role change can require you to reload before saving.
Managing members
From the Team page, the owner can:
- Edit a member's name, email, or role
- Reset a member's password
- Remove a member (immediately revokes access)
Access control
Role permissions are enforced at the server level:
- Viewers cannot perform any write operations (POST, PUT, DELETE) - the API returns 403
- Editors cannot access the Settings page or Team management
- Navigation automatically adjusts - pages you don't have access to are hidden
- Notes are private to each user - Owner and Editor notes are separate and not visible to each other. Viewers do not have access to Notes
- Board is visible to all roles - Owners and Editors can create and manage cards, Viewers can only view
If someone opens a restricted page directly, Studio denies access. The application can expose a narrow safe settings read to authenticated users for its interface; that does not grant configuration writes.
External access
A Studio MCP connection belongs to a current account and has its own scopes. The account’s current role remains a ceiling, including on retries. Revoking a connection, deleting its account or reducing its role can block further use.
External team and credential administration requires an exact owner-approved request. If the original actor loses access during an operation, the owner can inspect retained recovery instead of impersonating that actor. See Administration.
Found a mistake in these instructions? Open an issue.
Download VoxelSite