Team Management
Contentrain Studio uses a two-tier role system for access control. Workspace roles govern high-level access, while project roles provide fine-grained permissions within individual projects.
Inviting Members
Workspace Invitations
To invite a new member to your workspace:
- Navigate to Workspace Settings > Members
- In the Invite member section, enter the invitee's email address
- Select a workspace role (Admin or Member)
- Click Invite
The invitee receives an email with a link to join your workspace. They can sign in with Google OAuth or a magic link — GitHub OAuth is not required for invited members.

TIP
You can resend an invitation if the original email was missed. Click the Resend invite (envelope) button next to any pending invitation in the members list.
Invitation States
| State | Description |
|---|---|
| Pending | Invitation sent, not yet accepted (accepted_at is null) |
| Accepted | Member has signed in and joined the workspace |
| Expired | Invitation is more than 30 days old and still not accepted; shown in red in the members list. Resend it to invite again. |
Workspace Roles
Every workspace member has exactly one workspace role:
| Role | Capabilities |
|---|---|
| Owner | Full control — billing, settings, member management, transfer ownership, delete workspace. Every workspace has exactly one owner. |
| Admin | Invite and remove members, manage settings, billing, and project access, and access all projects implicitly. Cannot change member roles, transfer ownership, or delete the workspace. |
| Member | Access only explicitly assigned projects. Cannot manage workspace settings or members. |
Implicit Project Access
Workspace Owners and Admins have implicit access to all projects in the workspace. They do not need explicit project member assignments.
Workspace Members must be explicitly assigned to each project they need to access through project-level member management.
Changing Roles
Only the workspace Owner can change a member's workspace role. To do it:
- Navigate to Workspace Settings > Members
- Find the member in the list
- Use the role dropdown to change between Admin and Member
WARNING
You cannot change the Owner role through the dropdown. Use the ownership transfer feature instead. You also cannot change your own role.
Removing Members
To remove a member from a workspace:
- Navigate to Workspace Settings > Members
- Click the remove button next to the member
- Confirm the removal
Removing a workspace member also removes their project-level assignments within that workspace.
Project Roles
Project roles control what a member can do within a specific project:
| Role | Content | Models | Branches | AI Chat |
|---|---|---|---|---|
| Editor | Create, edit, delete | View | View, create | Content tools (no model changes) |
| Reviewer | View | View | Merge, reject, request changes | Read and review tools (no content edits) |
| Viewer | View only | View | View only | Read only |
Reviewer & Viewer require Enterprise Edition
The Reviewer and Viewer roles are available on Starter and above on the managed service, but they are Enterprise Edition capabilities (requires_ee). They only function when the enterprise bridge and the plan feature are present. Assigning Reviewer or Viewer on a plan without the feature is rejected. In a self-hosted Community Edition deployment (no ee/), new Reviewer or Viewer assignments are rejected, and an existing Reviewer or Viewer record degrades to Editor — read/write access with no review separation.
Editor
Editors are the primary content creators. They can:
- Create, update, and delete content entries
- Use the AI chat to perform content operations
- Create content branches through edits
- View branches and their diffs
Reviewer
Reviewers focus on quality control. They can:
- View all content (read-only)
- Review branch diffs
- Merge or reject content branches
- Use the AI chat for read operations
TIP
The Reviewer role is ideal for editors-in-chief or content managers who approve content but do not create it directly.
Viewer
Viewers have read-only access. They can:
- Browse content entries
- View model schemas
- View branch diffs
- Use the AI chat for read-only queries
Assigning Project Members
To assign a workspace member to a project:
- Navigate to Workspace Settings > Members (workspace owners and admins only)
- In the Project Access section, select the project
- Enter the member's email
- Select a project role (Editor, Reviewer, or Viewer)
- Click Assign
If the email does not belong to a workspace member yet, Studio invites that person as a workspace Member and assigns the project role in one step. The invite counts against your plan's team-member limit. Project settings has no Members tab.
Model-Specific Access (Pro)
On Pro and Enterprise plans, you can restrict a project member's access to specific models:
- Send
specificModels: trueand anallowedModelslist of model IDs when assigning the member throughPOST /api/workspaces/{workspaceId}/projects/{projectId}/members - The member will only see and interact with the selected models
The Project Access form in the app does not expose this setting; it is available through the API only.
This is useful for large projects where different team members manage different content areas (e.g., marketing team manages marketing models, docs team manages documentation).
Enterprise Edition capability
Model-specific access is gated by the roles.specific_models feature (Pro and above) and also requires the Enterprise Edition bridge (requires_ee). On Free and Starter plans, and in a self-hosted Community Edition deployment, specificModels is always treated as off (full model access).
Permission Matrix
Complete permission breakdown:
| Action | Owner | Admin | Editor | Reviewer | Viewer |
|---|---|---|---|---|---|
| View content | Yes | Yes | Yes | Yes | Yes |
| Create/edit content | Yes | Yes | Yes | No | No |
| Delete content | Yes | Yes | Yes | No | No |
| Merge branches | Yes | Yes | No | Yes | No |
| Reject branches | Yes | Yes | No | Yes | No |
| Use AI chat (write) | Yes | Yes | Yes | No | No |
| Use AI chat (read) | Yes | Yes | Yes | Yes | Yes |
| Manage models | Yes | Yes | No | No | No |
| Manage project settings | Yes | Yes | No | No | No |
| Manage workspace settings | Yes | Yes | No | No | No |
| Invite and remove members | Yes | Yes | No | No | No |
| Change member roles | Yes | No | No | No | No |
| Manage billing | Yes | Yes | No | No | No |
| Transfer ownership | Yes | No | No | No | No |
| Delete workspace | Yes | No | No | No | No |
Transferring Ownership
Ownership transfer lives in your personal account settings, not in the workspace Members tab. To transfer a workspace you own:
- The target member must have the Admin role
- Click your name at the bottom of the sidebar and open the Account tab
- In the Danger Zone, click Transfer Ownership next to the workspace and choose the new owner
- The previous owner becomes an Admin
The Danger Zone lists a workspace here only while it has other members, and a personal (primary) workspace cannot be transferred. See Account Settings.
WARNING
Ownership transfer is immediate and cannot be undone from the UI. The new owner has full control including billing, member management, and workspace deletion.
Removing Project Members
To remove a member from a project:
- Navigate to Workspace Settings > Members
- In Project Access, select the project
- Click the Remove member (trash) button next to the member
This only removes the project assignment — the member remains in the workspace and can be reassigned to other projects.
Authentication Methods by Role
Roles do not depend on how someone signs in. Any of GitHub OAuth, Google OAuth, or a magic link can create an account that owns a workspace, and invited members can use any method too. GitHub sign-in matters only for installing the GitHub App and connecting repositories (see Authentication).
Plan Limits
| Feature | Free | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Team members | 1 | 3 | 25 | Unlimited |
| Reviewer role (EE) | No | Yes | Yes | Yes |
| Viewer role (EE) | No | Yes | Yes | Yes |
| Model-specific access (EE) | No | No | Yes | Yes |
| Conversation API keys (EE) | 0 | 0 | 15 | Unlimited |
| API credits/month | 0 | 0 | 450 | Unlimited |
| MCP Cloud keys | 0 | 1 | 15 | Unlimited |
| MCP Cloud calls/month | 0 | 5,000 | 150,000 | Unlimited |
| Outbound webhooks (EE) | 0 | 3 | 25 | Unlimited |
Rows marked (EE) are Enterprise Edition capabilities — available on the managed service but hidden in a self-hosted Community Edition deployment. See Billing & Plans for the full feature matrix.
Next Steps
- Workspaces — Manage workspace settings
- Authentication — Understand sign-in methods
- Billing & Plans — Upgrade for more team members