Skip to content

Workspaces ​

A workspace is the top-level organizational unit in Contentrain Studio. It groups your projects, team members, billing, and GitHub App installation into a single boundary.

Workspace Types ​

Studio has two workspace types:

Personal Workspace ​

Every user gets a personal workspace automatically when they sign up. This workspace:

  • Is created on your first sign-in, with any method (GitHub, Google, or magic link)
  • Has type: primary in the system
  • Cannot be deleted (it is tied to your account)
  • Serves as your default workspace if no other is selected

Team Workspace ​

You can create additional team workspaces for collaboration:

  • Has type: secondary in the system
  • Can be renamed, configured, and deleted
  • Supports multiple members with different roles
  • Has its own billing plan and GitHub App installation

Workspace Dashboard ​

When you navigate to /w/:slug, you see the workspace dashboard. This page displays:

  • A header with the workspace name and project count
  • Two action buttons: Use Template and Connect repository
  • A grid of project cards showing your connected repositories
  • Empty states when no GitHub App is installed or no projects exist

Workspace dashboard showing the project grid with cards

Empty States ​

The dashboard shows contextual empty states:

  1. No GitHub App installed — prompts you to install the Contentrain GitHub App with an illustration and action button
  2. App installed but no projects — prompts you to connect a repository or start from a template

Creating a Workspace ​

To create a new team workspace:

  1. Open the workspace switcher in the sidebar and click Create workspace, or open the command palette with Cmd+K (or Ctrl+K) and run "Create workspace"
  2. Enter a workspace name
  3. The workspace is created and you are switched to it

TIP

Studio derives the URL slug from the name. Slugs must be unique and URL-safe, and form part of your workspace URL: /w/your-slug. You can change the slug later in the Overview tab.

Switching Workspaces ​

You can switch between workspaces in several ways:

  • Sidebar: Click the workspace name in the sidebar to open the switcher
  • Command palette: Press Cmd+K and search for a workspace name
  • Direct URL: Navigate to /w/:slug directly

The workspace switcher: your workspaces with plan badges and a "Create workspace" option

Studio remembers your last active workspace and restores it on your next visit.

Workspace Settings ​

Access workspace settings from the sidebar Settings link or by navigating to /w/:slug/settings. Settings are organized into tabs: Overview, Members, Billing, GitHub, Connected apps, and AI. The Members and GitHub tabs are visible to workspace owners and admins only, and the AI tab is hidden in self-hosted Community Edition. (Your personal profile lives separately in account settings.)

Overview ​

General workspace information:

  • Workspace name (editable)
  • Workspace slug (editable; changing it updates every workspace URL)
  • Plan card (on managed deployments, click it to compare or change plans)
  • Danger Zone: delete workspace (secondary workspaces, owner only)

Workspace settings — the Overview tab with name, slug, and plan, plus tabs for Members, Billing, GitHub, Connected apps, and AI, and the danger zone

Members ​

Team management:

  • View all workspace members and their roles
  • Invite new members by email
  • Change member roles (Admin or Member; owner only)
  • Assign members to projects (Project Access)
  • Remove members
  • Resend pending invitations

See Team Management for details.

Billing ​

Subscription and plan management:

  • Current plan and billing state
  • Trial status and days remaining
  • Upgrade/downgrade options
  • Customer portal access (owners and admins; every member can see the plan and usage)

See Billing & Plans for details.

GitHub ​

GitHub App integration:

  • Current installation status
  • Link to install or reconfigure the GitHub App
  • Connected repositories overview

The GitHub tab: the connected GitHub account with its repository access, Manage Permissions and Refresh buttons, and the list of accessible repositories

Connected apps ​

Third-party applications (Claude, ChatGPT, Codex) that signed in to the workspace with OAuth over remote MCP:

  • Copy the workspace's remote MCP endpoint and the connect snippets
  • Review connected apps and the scopes they were granted
  • Disconnect an app at any time

API keys for CI and headless agents are not here: they live in each project's settings (Project settings → API keys). See Connected Apps and the MCP Connector.

AI ​

Your own Anthropic API key (BYOA, Bring Your Own API Key). It is personal: it is encrypted, visible only to you, and each member adds their own.

  • Add your own Anthropic API key
  • View and delete your key

Plans without BYOA see an upgrade prompt in this tab; Community Edition hides it.

See AI Chat for details.

Workspace Hierarchy ​

Understanding how workspaces relate to other entities:

Workspace hierarchy A workspace, the billing and team boundary, holds a GitHub App installation, members with the owner, admin or member role, an AI key per member, billing through the configured payment provider, and projects. Each project has models, content, branches, media, forms, API keys and webhooks. User Workspace billing & team boundary in a workspace GitHub App installation Members owner · admin · member AI key per member BYOA Billing configured payment provider Projects connected repositories in each project Models Content Branches Media Forms Webhooks API keys MCP, Conversation API, CDN

Key Rules ​

  • A workspace owns its projects — deleting a workspace removes all its projects
  • The workspace's GitHub App installation determines which repositories are available to connect
  • Billing is per-workspace — each workspace has its own plan
  • Members are invited at the workspace level and then assigned to specific projects

Deleting a Workspace ​

WARNING

Deleting a workspace permanently removes all its projects, content configurations, and member assignments. This action cannot be undone.

To delete a secondary workspace:

  1. Navigate to Settings > Overview
  2. Scroll to the Danger Zone (visible to the workspace owner only)
  3. Click Delete Workspace
  4. Type the workspace name to confirm. Optionally switch on Also uninstall GitHub App (shown when the workspace has a GitHub App installation) and Also cancel active subscription (shown when it has one)

Personal (primary) workspaces cannot be deleted — they are removed only when you delete your account.

Transferring Ownership ​

Workspace owners can transfer ownership to another Admin member from their account settings, not from workspace settings:

  1. Click your name at the bottom of the sidebar and open the Account tab
  2. In the Danger Zone, click Transfer Ownership next to the workspace
  3. Choose the new owner
  4. The previous owner becomes an Admin

Only team (secondary) workspaces with other members appear there; a personal workspace cannot be transferred. See Account Settings.

TIP

Only Admin members can receive ownership transfers. Promote a Member to Admin first if needed.

Next Steps ​

Released under the AGPL-3.0 License. Privacy