# Organisation settings, audit log and publishing history > Change the organisation's name and feature flags, see who changed what across every space, and see what has gone live on a website. Source: https://docs.bifrostorbit.com/cms/editors/organisation-pages/ The organisation's pages are in the sidebar under **Organisation**, when you are on the space list rather than inside a space. To get there from a space, choose **All spaces** in the menu at the top of the sidebar. You only see the pages your role allows. **Members** and **Roles** are covered in [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/). **Bin** is covered in [Restore something deleted](https://docs.bifrostorbit.com/cms/editors/bin-and-restore/). ## Settings **Organisation › Settings** applies to every space in the organisation. Everyone can see it; Administrators and Owners can change it. Choose **Save changes** when you are done, or **Discard** to put back what was saved. ### General - **Name:** how the organisation is shown across the CMS. - **Slug:** a short name in lower case with no spaces. Changing it is safe: space and page addresses do not use it, so nothing that links to the CMS breaks. - **Contents:** how many spaces and members the organisation has. ### Content defaults **Default locale** is the locale every new region starts with, as its default, in any space. Regions that already exist keep their own locales, so changing it does not change them. ### Feature flags A flag is a switch the website and the editor can read, to turn something on for this organisation before everyone else. Type a name and choose **Add flag**, then turn it on or off with its switch. Only add one when a developer asks you to. ## Audit log **Organisation › Audit log** records who changed what, in every space: members added or removed, roles changed, spaces created and erased, keys issued and revoked, redirects and menus edited, and more. Developers, Administrators and Owners can read it. Each entry shows the **Action**, the **Detail** and the space it happened in, **Who** did it, and **When**, in UTC. Changes made by an AI agent or with an API key say so. Narrow the list by space, person, action, or a range of dates. **Clear filters** shows everything again. **Export CSV** downloads the entries that match your filters, up to 10,000 at a time, with the time, who, what, the space and the IP address. Entries stay after what they describe has gone. When a space is erased, the entry saying who erased it is kept. On the Starter plan the audit log shows the last 30 days, and on Growth the last 365 days. Enterprise shows everything. The filters, the list of people and actions, and **Export CSV** all stay within that window. Older entries are kept, not deleted, and are shown again after an owner upgrades under Billing in Orbit. A note at the end of the list says when older entries are hidden. Changes to pages are not in the audit log. They are in each space's publishing history, below, and in each page's version history. ## Publishing history Inside a space, open **Publishing › History** to see everything that has gone live on the website: pages published or unpublished, rollbacks, promotions between environments, and releases going out. Editing a draft is not listed, because nothing has reached a visitor yet. Each entry shows **What** happened, the **Page** and its address, **Where** (the environment and language), **Who** did it, and **When**, in the space's time zone. Choose a page to open it. Use the list at the top to show one environment or **Every environment**. The latest 200 entries are shown. An entry stays after its page is deleted, with the name and address as they were. ## Management tokens **Organisation › Management tokens** is for scripts and scheduled jobs that use the CMS on someone's behalf, such as a nightly redirect import. Developers, Administrators and Owners can create them. See [Management API](https://docs.bifrostorbit.com/cms/developers/management-api/) for how to use one. Choose **New token**, give it a **Name**, choose when it **Expires after**, and turn on **Read only** if it should change nothing. Choose **Create token** and copy it straight away: it is shown once. A token can do what you can do in this organisation and no more, and its changes show in the audit log under your name and the token's. To stop a token, open the menu on its row and choose **Revoke**. Anything using it is refused from its next request. Each plan includes a number of active tokens across the organisation: 2 on Starter, 10 on Growth and no limit on Enterprise. The page shows how many are in use. When the plan is full, **New token** is turned off until you revoke a token or an owner upgrades under Billing in Orbit. Revoked and expired tokens do not count.