> ## 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. # Branding and language > Put your organisation's name, logo and colours on Ainomos, and choose the language of the content Ainomos writes. Two settings decide how Ainomos presents itself to your people. **Branding** sets the names, logos, colours, footer and sign-in page. **Content language** sets the language of the drafts, proposals and rationales that Ainomos writes for you. ## Branding Who can do this: platform admins. Everyone in the organisation sees the result, and parts of it also show on the sign-in page before anyone signs in. **1. Open Branding** Open **Settings**, then **Branding**. **2. Change the fields you need** Every field says where it shows. The **Preview** beside the form shows the left rail as your people will see it, and follows every keystroke. **3. Save** Click **Save**. The page confirms "Saved. Changes visible after reload." Reload the page to see the change across Ainomos. ### Identity | Field | What it does | Where it shows | | - | - | - | | **App name** | Your organisation's name for this workspace. | At the top of the rail and in the browser tab. | | **Product name** | A name shown instead of "Ainomos", up to 60 characters. Leave it empty to keep "Ainomos". | In the browser tab and on the sign-in page. | | **Environment** | Marks a non-production workspace. Choose **None (production)**, **DEV**, **TEST**, **UAT** or **DEMO**. | In the emblem's corner on every page, on the sign-in page, and before the browser tab's title. Production shows nothing. | The setup instructions that AI apps follow name the Ainomos connection after the **App name** and the **Environment**, for example "Brain-DEV". This keeps two Ainomos workspaces apart on one computer. ### Colour & Theme Start from a preset under **Quick start**: **Red**, **Blue**, **Green** (the default) or **Grey**. Then adjust any colour with its colour picker or a hex value such as #0a84ff. | Colour | Used for | | - | - | | **Primary** | Your brand colour: main buttons, links, highlights. | | **Surface** | The page background. | | **Surface (alt)** | Secondary backgrounds such as panels. | | **Text** | Normal text. | | **Text muted** | Hints and secondary text. | | **Border** | Lines and field outlines. | Ainomos works out lighter, darker and text-on-brand variants of your primary colour automatically. To set them yourself, open **Advanced variants**: **Primary light**, **Primary dark**, **Text on primary** and **Text strong**. In the contrast check, Ainomos checks each text colour against its background, including on a dark screen, and marks any pair that falls below the level. A warning does not stop you from saving. It tells you that some people may struggle to read that text. Switch the preview between **Light** and **Dark** to check both. On a dark screen, Ainomos lifts your brand colour if it would disappear. **Reset colours to default** returns all colours to the default theme. ### Logos | Field | What it does | Where it shows | | - | - | - | | **Emblem** | A square logo. | In the rail, on the sign-in page and in invitation emails. | | **Favicon** | The small icon in the browser tab. If empty, Ainomos uses the emblem. | In the browser tab. | Click **Choose file** to upload. Ainomos accepts SVG, PNG, JPEG and WebP files up to 200 KB. ### Sign-in page Tick **Show this workspace on the sign-in page** to show your departments and teams, your chat models and the date your workspace started to anyone who opens your address. Project rooms are never shown. Leave it unticked to show only your branding. ### Footer | Field | What it does | Where it shows | | - | - | - | | **Footer line** | One line of text, for example "Nimbus Brain DEV · operated by Nimbus IT Services". | Under the account button at the foot of the rail, and on the sign-in page. | | **Links** | Links with a **Label** and a **URL**, for example to help, your privacy notice or your terms of use. Click **＋ Add link** to add one. | After the footer line. | ### Undo changes Most fields have a **Reset to default** button that clears your value and brings back the default. **Reset everything to default** at the foot of the preview does this for every field at once. ## Content language **Content language** decides the language of new content that Ainomos writes with a model: decision drafts, dreaming proposals, rationales and summaries. You can choose **German** or **English**. It does not change: * **The interface language.** Each person chooses that for themselves in the **Account** menu, under **Switch language**. * **Existing content.** Documents, decisions and drafts that already exist stay in the language they were written in. * **Chat answers.** An answer follows the language of the question. Who can do this: platform admins. **1. Open Content language** Open **Settings**, then **Content language**. The page shows the current value, for example "Currently: English". **2. Choose the language** Click **German** or **English**. Ainomos saves at once and confirms "Saved." The change is recorded as evidence, with the old and the new value. ### How drafts follow the content language * **Drafts Ainomos builds** use section headings in the content language. In English, a decision draft has **Context**, **Options** and **Recommendation**. A draft taken from a chat answer has **Context**, **Question** and **Proposal**. * **Drafts from AI apps.** When an app connected through MCP, the open standard AI apps use to connect to Ainomos, proposes or revises a draft, Ainomos checks the language first. If the text is clearly in the other language, Ainomos stores nothing and asks for the text again in the content language. Short or mixed text, such as a title or a list of code, passes. * **Imported decision files.** A record in the other language is not refused. The import marks it with a language warning, because a historical record stays as it was written. * **Rule messages.** When a rule blocks an answer, the rules that ship with Ainomos show their title and statement in the content language. Rules your organisation wrote or edited show exactly as stored. ## Related * [Settings](https://docs.ainomos.ch/admin/settings-overview.md) * [Decisions](https://docs.ainomos.ch/knowledge/decisions.md) * [Dreaming](https://docs.ainomos.ch/knowledge/dreaming.md) * [Signing in](https://docs.ainomos.ch/get-started/signing-in.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.