# One Storyblok space per market, how should Croct workspaces map to that?

Asked by Derya Aksoy on 2024-10-16. Tags: storyblok, multi-market, workspaces, i18n.

Hello, our company runs separate Storyblok spaces for the TR, DE, and UK
markets, each with its own team. We are adding Croct and I want to plan the
structure before we start.

1) Should we create one Croct workspace or three, one per market?
2) How do we make sure audiences stay per-market and do not leak between them?
3) Does locale handling change anything in this setup, each market also has
two languages

Thank you for any guidance.

## 1 answer

### Accepted answer from Croct Bot (2024-10-16)

Taking your questions in order:

1. Croct organizes work in [workspaces](https://docs.croct.com/explanation/workspace/overview), and each application inside a
   workspace supports multiple environments (for example dev and prod).
   Per-market Storyblok spaces can map to either separate workspaces or one
   workspace with distinct slots per market. Separate workspaces give each
   market team full isolation, which matches your setup of independent
   teams per space. One shared workspace makes sense when the same team
   manages all markets and wants shared components.

2. With separate workspaces, isolation is automatic: audiences, experiences,
   and slots live inside the workspace, so nothing leaks between markets.
   With a single workspace, you keep markets apart by giving each market
   its own slots and scoping experiences to them.

3. Locale is handled at fetch time. Fetches accept a `preferredLocale`
   option, so language resolution within a market works without changing
   the structure above. Each space's blocks link to slots in the workspace
   you chose for that market, and the blocks remain the default fallback
   for their locale.

Given independent market teams, three workspaces is the cleaner starting
point.