# Set up a new space

> A checklist from an empty organisation to a website your team can edit and publish: regions, the space, the website connection, people, reviews and launch.

Source: https://docs.bifrostorbit.com/cms/editors/new-space-checklist/

Work through these in order when your organisation starts a new website in CMS Orbit. Each step says who usually does it. Most take a few minutes; connecting the website is a developer's job and takes longer.

## 1. Add your regions in Orbit

**Who:** an owner or admin in Orbit.

CMS Orbit's regions match your organisation's regions in Orbit, so add those first: open your organisation in Orbit, choose **Settings**, then **Add region** under **Regions**. A website for Norway and Germany needs both, such as *Norway* and *Germany*. See [Add your regions](https://docs.bifrostorbit.com/orbit/admins/regions/).

While you are there, tick CMS Orbit for everyone who will work on the website, under **Members**.

## 2. Create the space

**Who:** an Administrator or Owner in CMS Orbit.

Choose **Add space** and follow the wizard: the name and logo, a template, the environments, and the regions and languages the website serves. Pick the template closest to your kind of website: its sample pages show in the preview straight away. Choose **Start from scratch** only if a developer is building the website's own components. See [Create a space](https://docs.bifrostorbit.com/cms/editors/create-a-space/).

## 3. Check regions and languages

**Who:** a Developer, Administrator or Owner.

Open **Configuration › Environments**. Check each region's address prefix, such as `/de`, its currency and its time zone, and that every language is there. The first language of a region is its default. Do the same for both Staging and Production.

## 4. Go through the space's settings

**Who:** an Administrator or Owner.

Open **Configuration › Settings** and decide:

- the **Timezone** used for scheduled publishing;
- what the website does **when a page is missing in a region**;
- whether to **keep the old URL working when a page moves**, so moved pages redirect by themselves;
- whether to **offer machine translation**;
- the workflow **Stages** your team uses, if any;
- how long things stay in the **bin**.

See [Change a space's settings](https://docs.bifrostorbit.com/cms/editors/space-settings/).

## 5. Connect the website

**Who:** a developer.

Open **Configuration › Website code**, where a new space opens by itself. The developer picks a starter, creates a public key (`cms_pk_`) and, for previews, a preview key (`cms_sk_`) for Staging, and gets the code on GitHub or deploys it to Vercel or Netlify with the settings filled in. Then they add the staging website's address as the **Preview URL**, so editors see the real website beside each page, and choose **Check the website**. Saving the Preview URL needs an Administrator or Owner. See [Get the website code](https://docs.bifrostorbit.com/cms/developers/get-the-website-code/), or [Connect a website](https://docs.bifrostorbit.com/cms/developers/connect-a-website/) to build one from an empty project.

Until then, the editor works, but the preview can't show your website.

## 6. Give people access

**Who:** an Administrator or Owner.

Under **Configuration › Access**, add each person with the role they need, and limit them to some regions where that makes sense: the Bergen team, for example, may only need Norway. See [Give someone access](https://docs.bifrostorbit.com/cms/editors/people-and-access/) and [Roles and permissions](https://docs.bifrostorbit.com/cms/editors/roles-and-permissions/).

## 7. Decide what needs a review

**Who:** a Developer, Administrator or Owner.

Choose which content types need approval before publishing, under **Schema › Content types › Approval**, and the steps they go through, such as Product safety, then Legal. Add approved wording for claims your pages repeat. See [Governance](https://docs.bifrostorbit.com/cms/editors/governance/).

## 8. Fill in what every page shares

**Who:** editors.

- **Site settings** such as contact details and the footer text. See [Change site settings](https://docs.bifrostorbit.com/cms/editors/site-settings/).
- **Menus** for the header and footer. See [Build a menu](https://docs.bifrostorbit.com/cms/editors/navigation/).
- **Redirects** from the old website's addresses, many at once from a spreadsheet. See [Create and import redirects](https://docs.bifrostorbit.com/cms/editors/redirects/).

## 9. Practise in Staging

**Who:** everyone who will edit.

Each person makes a page called **TEMP practice** in Staging, publishes it and deletes it again, following [Your first page, from draft to live](https://docs.bifrostorbit.com/cms/editors/getting-started/). Nothing in Staging reaches the public.

## 10. Launch

**Who:** an Administrator.

- To keep Production out of search engines until launch day, turn on **Hide from search engines** on the environment under **Configuration › Environments**. Turn it off on the day.
- Promote the pages from Staging to Production with **Promote to › Production**. See [Publish, schedule and take offline](https://docs.bifrostorbit.com/cms/editors/publish-and-schedule/).
- Open **SEO › Health** and the accessibility report, and fix what they find. See [Improve SEO health](https://docs.bifrostorbit.com/cms/editors/seo-health/) and [Work through the accessibility report](https://docs.bifrostorbit.com/cms/editors/accessibility-report/).
