> ## Documentation Index > Fetch the complete documentation index at: https://docs.ainomos.ch/llms.txt > Use this file to discover all available pages before exploring further. # Settings > Find every organisation-wide setting in Ainomos, see what it is for, and jump to the page that explains it. **Settings** is where platform admins configure Ainomos for the whole organisation: how it looks, who may do what, which models it uses, where audit events go, and what happens when something breaks. Settings that belong to one room, such as its members and rules, are managed in the room itself. See [rooms](https://docs.ainomos.ch/admin/rooms.md). ## Who sees Settings Who can do this: platform admins. The **Settings** entry appears in the account menu only for people with the Platform admin role. Anyone else who opens the address sees a notice that the page is only for platform admins. To give someone the role, see [roles](https://docs.ainomos.ch/admin/roles.md). ## Open Settings **1. Open the account menu** Click your name at the foot of the left rail. The menu is labelled **Account**. **2. Choose Settings** The page **Platform settings** opens. It shows every setting as a tile, sorted into six groups. **3. Open a tile** Each settings screen shows the name of its group above the title, and a **Back** button that returns you to the overview. ## Find a setting Type in **Search settings** at the top of the page, for example "SSO", "logs" or "roles". The search looks at each tile's title, its description, its group and a list of common terms. So "SIEM" finds **Log shipping**, "SMTP" finds **Mail server**, and "S3" finds **File storage**. Upper and lower case and accents make no difference, and German spellings such as "ae" for "รค" match too. While a search is active, a line such as "3 of 19 settings" tells you how many tiles match. Click **Reset search** to see all of them again. If nothing matches, the page says **No matching settings**. The search only narrows what you see. It does not change who may open a setting. ## The groups and their settings ### Appearance & language | Setting | What it is for | Explained in | | - | - | - | | **Branding** | Your organisation's name, logo, colours, footer and sign-in page. | [Branding and language](https://docs.ainomos.ch/admin/branding-and-language.md) | | **Content language** | The language of drafts, proposals and rationales that Ainomos writes, German or English. | [Branding and language](https://docs.ainomos.ch/admin/branding-and-language.md#content-language) | ### People & access | Setting | What it is for | Explained in | | - | - | - | | **Users** | Create accounts, activate them, and grant platform-admin and maintainer rights. | [Users](https://docs.ainomos.ch/admin/users.md) | | **Roles & permissions** | Who holds which role, and what each role may do. | [Roles](https://docs.ainomos.ch/admin/roles.md) | | **User visibility** | Whether members without a role can browse knowledge, decisions and the graph. | [Visibility](https://docs.ainomos.ch/privacy/visibility.md) | | **Identity & SSO** | Connect your own identity provider through OpenID Connect, such as Entra ID or Okta. | [Identity and SSO](https://docs.ainomos.ch/admin/identity-and-sso.md) | ### AI & data | Setting | What it is for | Explained in | | - | - | - | | **Models** | The model catalog: which models exist, which data classes each may process, and connecting your own models. | [Models](https://docs.ainomos.ch/models/overview.md) | | **Privacy settings** | How strictly Ainomos screens text for personal data, and which kinds of personal data it looks for. | [Personal data](https://docs.ainomos.ch/privacy/personal-data.md) | | **Memory & dreaming** | Pick a room and one of its memories, then manage its authority, visibility, owner, decision makers and dreaming. | [Memory](https://docs.ainomos.ch/knowledge/memory.md) | | **File storage** | Where Ainomos keeps the original files of imported documents. | [File storage](https://docs.ainomos.ch/admin/file-storage.md) | ### Governance & audit | Setting | What it is for | Explained in | | - | - | - | | **Audit log** | One read-only timeline of governed actions, their evidence records, and app reads. | [Audit log](https://docs.ainomos.ch/privacy/audit-log.md) | | **Log shipping** | Send audit events to Splunk, or let your SIEM fetch them. | [Log shipping](https://docs.ainomos.ch/privacy/log-shipping.md) | | **Connections** | Which apps people see, and every connected app with a switch to cut it off. | [Organisation apps](https://docs.ainomos.ch/apps/organisation-apps.md) | ### Operations | Setting | What it is for | Explained in | | - | - | - | | **System status** | Whether every system Ainomos depends on works, and since when. | [System status](https://docs.ainomos.ch/admin/system-status.md) | | **Maintenance** | Tell people about planned work, and close Ainomos or pause parts of it while it runs. | [Maintenance](https://docs.ainomos.ch/admin/system-status.md#maintenance) | | **Alert emails** | Who is emailed when a system goes down or works again. | [Alert emails](https://docs.ainomos.ch/admin/system-status.md#alert-emails) | | **Mail server** | The server that alert and maintenance emails are sent through, with a test. | [Mail server](https://docs.ainomos.ch/admin/system-status.md#mail-server) | ### Advanced These two settings have no page of their own. **Data import** loads a bundle into your organisation: a .zip file with rooms, knowledge, subscriptions, rules, decisions and agents, described by the guide on the page. Before anything is written, a preview lists what will be created, updated or skipped, and whether the bundle counts as demo material or as your own content. The same page offers shipped demo packs and **Clean up demo data**, which removes everything marked as demo and leaves your own content alone. **Platform Reset** returns the organisation to a clean state. Choose a scope: | Scope | What it deletes | | - | - | | **Demo data** | The seeded demo and sample data. Your own content stays. | | **Factory reset** | All rooms, memories, rules, agents and decisions. Only the platform infrastructure, the platform-admin identity and the empty top-level room remain. | The page first shows what the reset would delete and what stays protected. To confirm, you type the organisation's name exactly in **Tenant name**. If protected content sits inside a room the reset would remove, Ainomos refuses and deletes nothing. > [!WARNING] > > A factory reset deletes your organisation's content. Use it only on test or demo organisations. Who can do this: platform admins, for both settings. ## Related * [Roles](https://docs.ainomos.ch/admin/roles.md) * [Branding and language](https://docs.ainomos.ch/admin/branding-and-language.md) * [System status](https://docs.ainomos.ch/admin/system-status.md) * [Audit log](https://docs.ainomos.ch/privacy/audit-log.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.