Guides · Administration
Spaces and settings
Creating, switching, renaming and deleting spaces, a starter model, every section of Settings and who may change it, the dashboard's ⌘K menu and its language.
A space is one site or project of your organization: its content model, content, assets, locales and API tokens. An organization with a marketing site and a help centre has two spaces. Spaces are shared by every Obelism product, so Improve's tests and flags and the numbers of a site belong to the same space as its content.
Every space has three environments, develop, staging and production, each with its own model and content.
Creating a space
Spaces in the sidebar lists the organization's spaces with how many content types and entries each has. Admins and developers create one there:
- Name: what the dashboard calls it; change it later in Settings.
- Default locale: its code (
en,nl-NL) and name. Add more locales in Settings. - Start with: an empty content model, or a starter model for a blog, a marketing site or docs, in every environment.
A new organization starts with one space, named right after creating the organization on www.obelism.studio, in English. The organization's page there lists its spaces and adds, renames, transfers and deletes them for every Obelism product. Agents create spaces with POST /api/agent/organizations/{org}/spaces (createSpace, with starter), and delete or transfer one with deleteSpace and transferSpace, which www answers.
Switching
The switcher at the top of the sidebar picks the organization, the space and the environment you work in. It is the same switcher in every Obelism product, and they remember the same organization and space: switch in Content, and Improve opens on the same space. A role per space means someone only sees the spaces they were given.
Settings
Settings in the sidebar (for admins and developers) holds everything about the space and the environment you're in: General (the space itself), Site (what the canvas and your site use), API & webhooks (how a site reads content) and, once a store is connected, Shopify (the content types that use it). The store itself is connected on the space's page on www, since Content and Media share it. Locales, members, Shopify and AI translation apply to the whole space; the others to the current environment only, so production has its own preview URL, tokens and webhooks.
| Page | Section | For | Applies to |
|---|---|---|---|
| General | Name | Renaming the space | Space |
| General | Locales | The languages the space publishes in, the default, fallbacks, and removing one | Space |
| General | Members | Roles per space: who may open this space, and as what | Space |
| General | Publishing | Open, or reviewed by an admin | Environment |
| General | Content model | Maintained in the dashboard, or in code | Environment |
| General | Transfer this space | Moving it to another organization, with everything in it | Space |
| General | Delete this space | Deleting it, with everything in it | Space |
| Site | Preview URL | Where the canvas loads your site, and where it shows products and collections | Environment |
| Site | Prompt editing | Workers AI, or your own model through a signed endpoint | Environment |
| Site | AI translation | Whether AI translates, into which languages, house style, and translating on save | Space |
| Site | Redirects | The old paths of moved pages | Environment |
| API & webhooks | Environment variables | Copy as .env: every product's ids and environment, and a line for each token a site needs | Environment |
| API & webhooks | API tokens | Delivery, preview and management tokens | Environment |
| API & webhooks | Webhooks | Requests to your site when content changes, and their deliveries | Environment |
| API & webhooks | Usage | Delivery API requests this month and per day | Space |
| Shopify | Shopify | Adding a product grid block and product or collection page types; the store itself is connected on www | Space |
Publishing review, members, transferring and deleting the space are for admins only. In production, agents read settings but don't change the preview URL or prompt endpoint, or create tokens and webhooks: a person does that here. Agents read and change the rest with GET and PATCH …/settings (getSpaceSettings, updateSpaceSettings).
Transferring a space
Transfer this space, above deleting it in Settings, moves the space to another organization you're an admin of, in every Obelism product: its content model, content, history and files in Content, its tests, flags and audiences in Improve, its events in numbers. Its id stays the same, and so do its API tokens, webhooks, allowed origins and Shopify store, so sites keep working without a change. Pick the organization, type the space's name, and confirm once more.
- Only an admin of both organizations transfers a space, and both have to be active.
- An organization's first space can't be transferred: sites that name only the organization, not the space, use it. That includes an organization's last space.
- Roles per space don't move along. In the new organization its members have their organization role in the space; members of the old one lose access unless they're in the new one too.
- The space keeps its slug, unless the new organization has a space with it: then it gets
-2. - Usage counted before the move stays with the old organization; from then on the space counts for the new one, under its plan.
Deleting a space
Delete this space, at the bottom of Settings, deletes the space in every environment: its content model, content, history, files, API tokens and webhooks. Type the space's name to confirm. Sites reading it stop getting content at once, and it can't be undone, so export what you want to keep first. An organization's last space can't be deleted. Only admins delete spaces.
The dashboard
- Home greets you with what needs you in the space you're in: unpublished changes, drafts, reviews, failed schedules and what is ready to promote, each with a link, then the numbers, the latest edits and where each environment stands. In a new space, developers and admins find the prompt that connects your coding agent there, ready to copy. Invites to other organizations show there to accept.
- ⌘K (Ctrl+K) opens one menu for every Obelism product: type to go to a page, or ask about the space in your own words ("which pages are still drafts?", "add an FAQ block to the pricing page"). It reads straight away and asks you to confirm every change before it is made, with your own role. It never creates tokens or webhook secrets, and doesn't upload files.
- The dashboard is in English or Dutch: Nederlands (or English) in the sidebar switches it for this browser.
- Organizations, members, invites and your account are managed on www.obelism.studio, for every Obelism product at once.