# Agency setup for five client Shopify stores, one Croct account or five?

Asked by Aisling Byrne on 2025-08-19. Tags: shopify, agency, workspaces, workflow.

We are an agency personalising five client storefronts. Until now we juggled
separate VWO contracts per client, which was a nightmare to administer, so
before we set anything up wrong I want to understand the account model.

Practical questions:

- Do we create one organisation with everything in it, or one per client?
- How do organisations, workspaces and applications map to five separate
  client stores?
- Most importantly, how is client data kept apart? Client A must never see or
  touch client B's visitor profiles, and billing needs a clean boundary too.

## 1 answer

### Accepted answer from Marcos Passos (2025-08-19)

The [mapping that works for agencies](https://docs.croct.com/explanation/organization/organizational-models) is one organization for the agency, one
workspace per client, one application per storefront.

Workspaces separate clients cleanly. Each client store is an application
inside that client's workspace, with its own app ID, so credentials never
overlap between clients. Team members are granted access per workspace, which
gives you the access boundary you are after: someone working on client A
simply does not see client B's workspace.

On the data side, the default [anonymity scope](https://docs.croct.com/explanation/application/anonymity-scope) is the workspace, so visitor
profiles never leak between client workspaces. A shopper known on client A's
store is a completely separate profile if they ever visit client B's store.

Each application also supports separate dev and prod environments with their
own credentials, which is handy for the staging themes agencies typically run
per client.

If some clients prefer to own their data and billing directly, the alternative
is a separate organization per client with your agency team invited in. Both
models work; the single-organization model is just less administration.

#### Reply from Aisling Byrne (2025-08-20)

Brilliant, that is exactly the structure I was hoping for. One org, five
workspaces it is. The per-workspace access is what sells it internally.
