# Best practice for an agency running Croct across several client Storyblok spaces?

Asked by omar_es on 2025-03-27. Tags: storyblok, agency, workflow, workspaces.

Tech lead at an agency, we manage five client sites, each in its own
Storyblok space. We are rolling Croct out across three of them this quarter
and I want to get the account structure right from day one instead of
untangling it later.

Requirements are the obvious ones: content, audiences, and analytics fully
separated per client, no chance of one client's data showing up in
another's dashboard. And within each client we need a dev/prod split so we
can test integration changes safely.

How do people structure this, one account per client or is there something
built for the multi client case?

## 1 answer

### Accepted answer from priya_builds (2025-03-27)

There is a built-in structure for this: workspaces. We run a very similar
agency setup and the pattern that works is one workspace per client
inside your organization. Slots, audiences, experiences, and analytics
all live at the workspace level, so the separation you want is the
default, not something you enforce with discipline. A client dashboard
only ever contains that client's data.

For the dev/prod requirement: applications support multiple environments,
so each client gets a dev and a prod environment with their own
credentials. Integration changes get exercised against dev before they
touch anything live, same rhythm as your Storyblok preview flows.

Then each Storyblok space links its blocks to slots in the corresponding
workspace, keeping the one-space-one-workspace symmetry. That mapping
discipline is the only thing you actually have to maintain by hand, and
it is worth writing down in your runbook so nobody wires a new block to
the wrong workspace in a hurry.

Five clients is well within where this stays manageable. The mistake to
avoid is cramming clients into one shared workspace to save setup time,
you lose the isolation and never get it back cheaply.