Orgs and Workspaces

How organizations and workspaces structure your Runstack account—Personal vs Team, workspace isolation, and team collaboration.

Source: https://runstack.engineer/docs/orgs-and-workspaces

Runstack organizes your account into one organization and one or more workspaces. Workspaces isolate chats, agents, toolkit connections, API keys, MCP servers, LLM settings, and guardrails so each project or team can run independently.

Organization types

When you sign up or in Settings → Organization → General, choose an organization type:

Both types share the same default workspace (defaultWS), created automatically on first login.

Switching organization type

Go to Settings → Organization → General, pick Personal or Team, and click Save changes. Switching to Team unlocks workspace member invitations (see below).

Workspaces

A workspace is the unit of isolation inside your organization. Everything operational lives inside the active workspace:

• Chats and chat history
• Studio agents (drafts and published)
• Toolkit connections (GitHub, Gmail, Notion, and others)
• API keys
• External MCP servers
• LLM provider credentials and model selection
• Guardrails

Switch workspaces from the sidebar workspace switcher. The active workspace is sent on every API request via the X-Workspace-Id header.

Creating workspaces (Team orgs)

Team organizations can create additional workspaces:

1. Open the workspace switcher in the sidebar
2. Click Create new WS
3. Enter a Name and optional Description
4. Click Create workspace

The new workspace becomes your active workspace. Workspace names must be unique within your organization (max 64 characters).

Personal organizations are limited to the default workspace and cannot create more.

Managing workspaces

Settings → Organization → Workspaces lists every workspace in your organization. From there you can:

• See which workspace is Default or Active
• Switch to workspace to make it active
• Manage settings for workspace-specific configuration

The default workspace cannot be deleted. You must always keep at least one workspace.

Team members (Team orgs only)

Team organizations can invite existing Runstack users to non-default workspaces.

Inviting a teammate

1. Switch to a workspace that is not the default workspace
2. Go to Settings → Workspace → Team Members
3. Enter the invitee's Email address (they must already have a Runstack account)
4. Click Send invitation

The invitee receives an in-app notification — not an email. They accept or reject from Settings → User → Notifications.

Requirements and limits

• Organization type must be Team (switch under Organization → General if needed)
• Only the organization owner can send invitations
• The default workspace cannot have team members — create or switch to another workspace first
• Invite statuses: Pending, Accepted, or Rejected

Once accepted, the member sees the shared workspace in their sidebar under your organization name.

Multiple accounts per app

Toolkit connections are workspace-scoped. Each workspace stores its own OAuth tokens per provider (GitHub, Gmail, Notion, Linear, Google Sheets, Google Calendar, and others).

Because agents, chats, and tool execution all resolve against the active workspace, you can connect different accounts for the same app across workspaces — for example, a personal GitHub in your default workspace and a work GitHub in a team workspace.

Connecting a provider again in the same workspace replaces the existing connection for that provider.

What is workspace-scoped?

Organization settings (name, type, workspace list) apply across the whole organization. User settings (account, notifications, appearance) are per user.