Multi-Workspace

Create and manage multiple workspaces — one user can belong to many workspaces, each with isolated data.

Overview

A workspace is an isolated environment in ZapTicket. Each workspace has its own conversations, tickets, agents, settings, branding, and API keys. Data never leaks between workspaces. This makes workspaces ideal for agencies managing multiple clients, companies with separate brands, or development/staging/production separation.

Creating a Workspace

Any authenticated user can create additional workspaces. The user who creates a workspace automatically becomes its first Owner.

Click the workspace switcher in the top-left corner of the dashboard.
Click Create Workspace.
Enter a name (e.g., "Acme Support") and a URL slug (e.g., "acme-support").
Click Create.

💡The URL slug must be unique across all ZapTicket workspaces. It's used in some URL paths and cannot be changed after creation. Choose something short and recognizable.

Create workspace via API

curl -X POST https://api.zapticket.app/api/workspaces \
  -H "Authorization: Bearer YOUR_USER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Support",
    "slug": "acme-support"
  }'

Switching Workspaces

If you belong to multiple workspaces, use the workspace switcher in the dashboard navigation to move between them. Switching workspaces changes the entire context — you'll see different conversations, tickets, settings, and team members.

The workspace switcher shows all workspaces you're a member of, with your role indicated next to each one. The currently active workspace is highlighted.

One User, Many Workspaces

A single ZapTicket account (identified by email) can be a member of unlimited workspaces. Your role and permissions are scoped per-workspace — you might be an Owner in one workspace and an Agent in another.

Workspace	Your Role	Access Level
Acme Inc	Owner	Full admin access
Beta Product	Agent	Conversations and tickets only
Client: BigCorp	Owner	Full admin access

💡Your notification preferences (email alerts, desktop notifications) are configured per-workspace. You won't receive inbox notifications from a workspace you're not actively using unless you've opted in to email notifications for that workspace.

Workspace-Scoped API Tokens

Every API token (both public site keys and secret keys) is scoped to a specific workspace. This means:

A site key only works for the widget connected to that workspace.
A secret key only has access to data within that workspace.
You cannot use a token from Workspace A to access data in Workspace B.
Each workspace has independent key pairs that can be regenerated without affecting other workspaces.

Token scoping

zt_pub_abc123  →  Workspace: "Acme Inc"     (widget only talks to Acme's inbox)
zt_sk_def456   →  Workspace: "Acme Inc"     (API calls only see Acme's data)
zt_pub_xyz789  →  Workspace: "Beta Product" (separate widget, separate data)
zt_sk_uvw012   →  Workspace: "Beta Product" (separate API access)

This isolation is enforced at the API layer. Even if a token is accidentally leaked, it can only access the data within its workspace — not your entire organization.

Workspace Data Isolation

Each workspace is completely isolated. The following are scoped per-workspace and never shared:

Conversations and message history
Tickets and ticket comments
Agent roster and roles
Branding configuration
Canned responses
API keys (public site key, secret key, identity secret)
Widget settings (greeting, offline message, position)

Use Cases

Agencies managing multiple clients

Create one workspace per client. Each client gets their own site key, branding, and isolated data. Your agents can be members of all client workspaces and switch between them.

Multiple brands or products

If your company operates multiple products or brands, each can have its own workspace with distinct branding, team, and support workflows.

Environment separation

Create separate workspaces for development, staging, and production. Use the development workspace's site key in your local environment so test conversations don't pollute production.

Workspace Limits

There is no hard limit on the number of workspaces you can create or belong to. However, each workspace counts toward your plan's usage limits (agents, conversations per month) independently.