Update · Published June 30, 2026

Agency Workspaces: run multiple client stores, and their AI agents, from one account

If you run more than one brand, or you run stores for other people, you've felt this pain: every client wants their own clean space, their own products, their own orders, and none of your other clients' work bleeding in. Agency Workspaces solve that. One account holds many isolated client workspaces, your team gets role-based seats, and (this is the part we're most excited about) you can hand an AI agent a key that's locked to one client and one role. Here's who it's for, what it does, and why it matters for where commerce is going.

Who it's for

Agency Workspaces are built for anyone running more than one store and tired of juggling more than one login:

• Print-on-demand agencies and design studios managing catalogs for multiple clients.
• Operators with several brands who want each brand kept cleanly separate.
• Teams where different people own different parts of the work: one person designs, another prices and lists, another runs orders.

If you've been spinning up a separate account per client, or sharing one messy account and hoping nobody touches the wrong store, this is the feature you've been waiting for.

What a workspace actually is

A workspace is an isolated space for one client or one brand. Each workspace has its own stores, its own products, its own designs, and its own orders. Switch the active workspace from the top of the app and everything you see (catalog, sync status, orders) is just that client's. Nothing leaks across the boundary.

One account can hold as many workspaces as you have clients. You invite your team once, as seats on the account, then assign each person to the workspaces they should touch. Billing is per seat, so the account grows with your team instead of with the pile of separate logins you'd otherwise be paying for.

The three pieces:

• Workspaces are one isolated space per client or brand.
• Seats are the people on your account.
• Roles are what each seat can do inside a workspace.

Roles: five seats that map to the work

Most permission systems give you "admin" and "everyone else." That's too blunt for commerce work, where the steps are genuinely different jobs. So workspace roles map to the actual pipeline: design, build, list, sell.

A Creator makes the thing. A Merchandiser prices it and lists it. An Operator runs the post-sale work. A Director oversees the whole workspace. A Viewer can look but not touch. You assign the role that fits the person and the client, and that's the boundary they work inside.

Agentic role assignments: the part we're most excited about

Here's where Agency Workspaces stop being "just" team management.

The same roles apply to AI agents. When you create an agent API key, you can scope it to one workspace and one role. That key can't see your other clients, and it can't do anything its role doesn't allow.

That sentence carries a lot of weight, so let me make it concrete:

• Give your designing agent a Creator key for a single client. It can generate designs and build products in that one workspace, and nowhere else.
• Give your fulfillment agent an Operator key. It can process orders and push tracking, but it literally cannot generate a design, because the Operator role doesn't hold the design-generation permission. That isn't a setting you have to remember to switch off. It's structural.
• Give a reporting agent a Viewer key. It can read and summarize, and that's all.

Image generation is the one metered action on the platform. It draws against the quota included in your plan, and only Director and Creator hold that permission. So an Operator or Viewer agent key is, by construction, incapable of burning through your image quota or wandering into a client it was never meant to touch. You're not trusting the agent to behave. You're handing it a key that can't misbehave.

This is least-privilege access, applied to software agents the same way you'd apply it to people. It's the difference between "I gave my agent the keys to everything and I'm hoping for the best" and "I gave my agent exactly the access this job needs."

How it ties into agentic commerce

We've written before about agentic commerce: the shift from chatbots that answer questions to agents that actually run merchandising work end to end. We've also covered the rails the payment networks built so agents can transact, and twelve real examples of AI doing live ecommerce work. The part nobody talks about enough is the bit in the middle: once you're delegating real commerce work to agents, how do you keep them bounded?

Agency Workspaces are the answer. The hard problem in agentic commerce isn't getting one agent to run one store. It's running many agents across many stores without one of them doing something expensive, or wrong, in the wrong place. Workspaces plus scoped roles give you exactly that: a clean boundary per client, a least-privilege key per agent, and a single human overseeing the whole thing.

This is what running an agentic ecommerce operation looks like in 2026. One operator. A roster of clients, each in their own workspace. A set of agents, each holding a scoped key for the job it does. The operator sets the policies and reviews the results. The agents do the work, inside lines they cannot cross.

The benefits, in one place

• Clean client separation. Every client gets an isolated workspace. No cross-contamination, no "wait, which store am I in."
• Least privilege for people and agents. Roles map to real jobs. A key, human or agent, only does what its role allows.
• Quota safety by construction. Only Creator and Director can generate images, so a scoped agent key can't burn through your plan's image quota on its own.
• Scale without headcount. One operator can oversee many clients and many agents at once, because the boundaries do the babysitting.
• Per-seat economics. You pay for the team you have, not for a stack of separate accounts.

Getting started

Agency Workspaces are part of the Enterprise plan. To set it up:

1. Open Team & Workspaces from your account menu.
2. Create a workspace for each client or brand.
3. Invite your team as seats and assign each one a role per workspace.
4. To put an agent on a client, go to Developer → API Keys, create a key, and choose the workspace and role to scope it to.

That last step is the one to play with. Issue a Creator key scoped to one client, point your agent at it, and watch it design and build inside a boundary it can't escape.

If you're running more than one brand, or building stores for other people, this is the cleanest way we know to do it, with people and agents, at the same time. Start here.