One Storyblok space per market, how should Croct workspaces map to that?
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.
- Should we create one Croct workspace or three, one per market?
- How do we make sure audiences stay per-market and do not leak between them?
- Does locale handling change anything in this setup, each market also has two languages
Thank you for any guidance.
1 answer
Taking your questions in order:
-
Croct organizes work in workspaces, 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.
-
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.
-
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.