Claude follows your workspace
One connector connection for the whole agency — switch client from Claude or in the app, and set up new clients without leaving the chat.
The obvious worry about running many clients through one Claude connection is that you'd have to reconnect every time you changed client. You don't.
You connect Claude once. It always works in whichever workspace you're currently in.
How it works
Tell Claude which client
Say "work on the Acme workspace". Claude switches with switch_workspace — or use the workspace switcher in the app's sidebar; both do the same thing.
Nothing to reconnect
No setting to change, no need to start a new chat.
Claude is now working on that client
From its next step, it reads that client's products, leads, brand voice, branding and Brain — and anything it creates lands in their workspace.
Your connection isn't tied to one client. It reads which workspace you're in each time it acts. An app tab you already have open keeps its own workspace until you switch there too.
Knowing which client Claude is on
Ask Claude to list your products. It reports the workspace those products came from, names the other workspaces on your account, and links you to the switcher.
The same happens when you create a product — Claude confirms which client it was created for, so a product built against the wrong workspace doesn't go unnoticed.
If you ask for a product from another client
Claude will tell you. Because a connection only reaches the workspace it's currently in, asking it to edit a product belonging to another client returns an explanation rather than a dead end: which workspace it's looking in, which other workspaces exist on your account, and a link to switch.
Ask it to switch, then ask again — nothing to reconnect.
Setting up a new client from Claude
On the Agency plan, a whole client set-up can happen in one conversation:
Create the workspace
"Create a workspace for Acme" — Claude creates it (create_workspace) and switches to it.
Set their brand voice
Tell Claude about the client, or paste their details, and it saves the brand voice (set_brand_voice) — including the business name and booking link their result pages use. Add their logo and colours with upload_image and set_design_system.
Connect their domain
"Use acme.youragency.com" — Claude gives you the DNS record (set_workspace_domain), then finishes activating it once the record is in place (get_workspace_domain_status). update_workspace sets where the bare domain sends visitors and its favicon.
Bring in products you've already built
"Copy the ROI calculator into Acme" — a complete copy, unpublished, ready for the client's branding (copy_product_to_workspace).
Hand over the leads
"Export Acme's leads" — a spreadsheet download link (export_data).
Let the client fill in their own details
Ask Claude to "send Acme a brand set-up form". It builds a short intake product in the client's workspace, on their domain (for example acme.youragency.com/brand-setup), asking the same questions as the Brand Voice page. When the client has filled it in, ask Claude to apply their answers: it shows you what it would save, and saves it only after you confirm.
If you work in two clients at once
Claude works in whichever workspace you switched to most recently. If you're moving between clients quickly, the safe pattern is one client per sitting: switch, confirm with a product list, build, then switch.
Using a key for a single client
If you'd rather have a connection that's permanently locked to one client — for a build machine or an automation that should never touch anything else — an API key can be pinned to a single workspace, and it ignores whatever you're doing in the app. Keys are managed under Settings → API.
For everyday agency work, the normal Claude connection following the app is what you want.