Modelling content
Teams & spaces
Bring your team in with the right level of access, and run every brand, region or outlet site from a single installation.
User roles
Three roles, assigned per user. Give people the lowest one that lets them do their job.
| Role | Can | Cannot | Typically |
|---|---|---|---|
| Super Admin | Manage spaces, users, imports, settings and all content | — | Ecommerce lead, technical owner |
| Editor | Create, edit and publish content; manage media | Manage users or spaces | Content manager, senior merchandiser |
| Author | Create and edit their own content | Publish, or edit other people's work | Copywriters, agencies, seasonal staff |
Add and manage people in Settings → Users. There are no per-model or per-field permissions — if you need a harder boundary than the Author role gives you, use a separate space.
Spaces
A space is a completely isolated content environment: its own models, entries, media library and API key. Nothing leaks between them.
For a retailer this is usually how you separate brands, regions and channels. A typical estate might look like this:
Example space layout
One installation, six spaces, one AWS bill
| Space | Used for | API prefix |
|---|---|---|
| UK store | Main storefront | /api/uk-store/ |
| EU store | European range and copy | /api/eu-store/ |
| Outlet | Clearance brand | /api/outlet/ |
| Wholesale | Trade portal content | /api/wholesale/ |
| In-store screens | Digital signage | /api/in-store/ |
| Staging | Rehearsing campaigns safely | /api/staging/ |
Spaces are logical rather than infrastructural. Running six costs no more to host than running one.
Working with spaces
- Switch spaces with the dropdown at the top of the sidebar. Everything you see afterwards belongs to that space.
- Call a specific space by prefixing any endpoint with its slug:
/api/uk-store/content. - Clone a space to duplicate its models, content and media references into a new one — the fastest way to launch a new region against a proven model.
- Give each space its own API key, so a key exposed in one storefront cannot read another brand's content.
GET /api/uk-store/content/model/product Authorization: Bearer UK_STORE_API_KEY
Spaces are how CloudSource does localisation. There is no field-level translation, so a market with its own language gets its own space. That suits teams whose ranges and merchandising genuinely differ by market. If you need the same entry in eight languages with shared structure, weigh this carefully — see the comparison.