Run an agency's client operations from Slab5: one workspace per client

Every agency runs the same five workflows for every client: inbound, content, projects, support, reporting. The trouble is each client wants their data separate, their access controlled, and their reporting tailored — and you don't want to operate ten copies of ten tools.

One workspace per client, inside a single Slab5 organization, fixes most of this.

Why one workspace per client

Workspaces are the operational boundary in Slab5. Putting each client in its own workspace gives you:

• Per-client API keys and MCP clients. You can hand a client their credentials at the end of the engagement without leaking other clients' data.
• Per-client audit logs and usage. Billing and accountability are clean.
• Per-client retention. If a client wants longer retention, scope the upgrade to their workspace.
• Per-client kill switch. Pause one client without affecting the others.

The organization above the workspaces gives you a place to keep agency-wide playbooks.

The handoff at engagement start

When a new engagement begins:

1. Create a workspace named for the client. 2. Provision an API key for your own tooling, an MCP client for any agents you run on their behalf, and (later) an OAuth grant for the client's team to access through their own AI assistants. 3. Seed the workspace with your standard collections: pages, blog posts, support queues, project tasks. Copy from your agency playbook workspace. 4. Set a workspace-level spend cap so a runaway agent or webhook cannot blow up a client's bill.

The setup takes about an hour. Templates make the next client take ten minutes.

Shared playbooks in your agency workspace

Keep one "agency" workspace with no client data — just your standard collection schemas, the prompts and scope sets you reuse, and templates for engagement kickoff. When you start a new client, you clone from this one.

The agency workspace also holds the agency's own CRM (your sales pipeline), CMS (your own website), and Tasks (internal work).

Reading across client workspaces

For agency-wide reporting ("how many active tickets across all clients right now"), use organization-level credentials with read scopes across the workspaces you operate. The BI module can query across workspaces for org owners.

Offboarding

When an engagement ends, you have two options:

1. Hand the workspace to the client. Transfer ownership; revoke your credentials. The client keeps everything, including the audit trail. 2. Export and archive. Use audit/usage export to hand the client a clean record; archive the workspace on your side.

Either way, no data is stranded in a shared CRM you can't fully detach from.

What this replaces

For most agencies: one HubSpot seat per client, plus a shared Notion that nobody trusts, plus a helpdesk shared across clients, plus a spreadsheet of project tasks. One workspace per client replaces all of it — with API access, agent access, and a clean offboarding story.

Per-client MCP clients with crm:read, support:read, tasks:write for triage and reporting. Org-level credentials for agency-wide rollups.

One workspace per client. Org-level API keys for cross-workspace reporting. Per-workspace spend caps and retention.