> ## 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. # Rooms > Create rooms, set them up in the room details, and see what passes down the room tree. A room is where Ainomos keeps the knowledge, rules and decisions of one part of your organisation, and where it decides who may use them. Every room has at least one owner, a list of members and a data class. Rooms form a tree: a team room sits inside its department, and the department sits inside the organisation. ## How rooms form a tree The top room is your organisation. Ainomos creates it when the organisation is set up, and it cannot be archived. Every other room has a parent room and a type: **Department**, **Team**, **Project** or **Special**. The type is a label and does not change what a room can do. If your organisation shows its structure on its sign-in page, department and team names appear there, project and special rooms never do. | Passes down to every room below | Copied once, when a room is created | Never passes down | | - | - | - | | Rules. A rule set in a room applies in every room below it. | The parent's deciders, who become members and deciders of the new room. | Membership. A member of a department is not a member of its teams, and the other way round. | | Knowledge. Answers in a room also draw on the decisions and documents of the rooms above it. | The parent's agent door, open or closed. | Owners and curators. Owning a room gives no rights in the rooms below it. | ## Create a room Who can do this: platform admins and owners of the parent room create a room directly. Other members of the parent room send a room request instead. **1. Open the form** Open the room picker at the top of the screen and choose **New Room**. The room you are in is preselected as the parent. **2. Fill in the fields** Use the table below. Under **Where it sits**, the form shows what the new room inherits: you as its owner, the parent's deciders per decision type, and the agent door. **3. Create or request** Choose **Create Room**. If you may not create rooms under this parent, the button reads **Request Room** and Ainomos files a request. | Field | What it does | | - | - | | **Name** | The display name. You can change it later. | | **Purpose, one line** | Required, up to 160 characters. Agents read it when they look for the right room. It becomes the room's first decision record. **Context** below it is optional. | | **Identifier** | Proposed from the name: lowercase letters, digits and single hyphens. Unique and permanent, because it is written into evidence, app identities and the access check. | | **Type** | Department, Team (the default), Project or Special. | | **Data class** | **C0, experimental**, **C1, internal**, **C2, confidential** (the default) or **C3, strictly confidential**. It decides which models may process the room's content. See [data classes](https://docs.ainomos.ch/privacy/data-classes.md). | | **Parent Room** | Where the room sits, and so what it inherits. | | **Continue numbering at** | Optional. For ADR, BDR and SDR, the number the first draft of that type gets, for teams that move records over from another tool. | You become the new room's owner and a member, and Ainomos writes an evidence record in the parent room. > [!NOTE] > > The room details show the data class and the parent room but offer no way to change them later. Choose both with care. ### Room requests A request has no identifier field: Ainomos derives it from the name on approval. Open requests appear under **Room requests** in the room details of the people who can act on them. **Approve** creates the room, and the person who asked becomes its owner. **Reject** needs a reason. The person who asked can **Withdraw** an open request. Who can approve or reject: platform admins and owners of the parent room. ## The room details Select a room, then choose **Room details** (the sliders button) in the bar at the top. Every member can open the drawer. What you can change depends on your responsibilities. The drawer shows, from top to bottom: * The room's facts: **Slug** (the identifier), **Data class**, **Type**, **Parent room** and **Your role**. * **Overview** and **Where it sits**: the room at a glance, the rooms above and below it, and how many rules, decisions and documents it inherits. * **Agents** and **Answers**: the settings below. * **Responsibilities** and **Members**. See [roles and permissions](https://docs.ainomos.ch/admin/roles.md). The members card shows only to owners and platform admins. * **Decision numbering**: the next key per type, and where it continues. * **Danger zone**: archiving. | Setting | What it does | Who can change it | | - | - | - | | **Agent door** | **Reachable** or **Closed** to connected apps. It protects the door, not the data: an open sub-room still passes this room's knowledge on. See [what apps can do](https://docs.ainomos.ch/apps/what-apps-can-do.md). | Owners | | **Agent instructions** | Whether the room briefs arriving apps. **Manage instructions** opens the editor. | Owners | | **Agent proposals** | How many open decision drafts one app or person can hold here. | Owners and room curators | | **Question translation** | On by default. Each question is also searched in the other language, German or English. Costs one small model call per question on the room's budget. | Owners | | **Source weights** | Which kinds of source count most in answers. See below. | Owners | | **Decision numbering** | Where the next ADR, BDR or SDR key continues. | Owners | Changes to agent proposals, question translation and source weights need a reason. Every change writes an evidence record. ### Source weights in plain words When Ainomos answers, it ranks the sources it found. Source weights tell it which kinds to prefer in this room: **Decision records**, **Room knowledge** (this room's and what it inherits), **Law**, and **Other subscribed brains** (knowledge the room subscribes to from elsewhere). | Weighting | Effect | | - | - | | **Neutral** | Every kind counts the same. | | **Engineering** | Decision records and room knowledge first, law lower. | | **Legal** | Law first. | | **Custom** | You set each kind from 0.25 to 2.0. 1.0 is neutral. | The room's purpose may suggest a weighting. **Apply suggestion** uses it; nothing is set automatically. Weights only reorder sources of the same standing, so a subscription marked authoritative stays first and a question about the law still finds the law. A change applies from the next question. ### A room without a purpose Rooms created by the setup wizard, or before purposes existed, may have none. Their owner sees the step **A purpose** in the room's setup card in Knowledge and can write it there. ## Rename or archive a room Who can do this: owners of the room. * **Rename**: choose **Change name** (the pencil next to the name), type the new name and choose **Save**. The identifier does not change. * **Archive**: in the **Danger zone**, choose **Archive**, then **Archive room**. The room leaves the room picker, the tree and agent routing. Its evidence stays findable. Archive child rooms first. The top room cannot be archived. Rooms cannot be deleted, moved or unarchived in the app. ## Related * [Roles and permissions](https://docs.ainomos.ch/admin/roles.md) * [Users](https://docs.ainomos.ch/admin/users.md) * [Data classes](https://docs.ainomos.ch/privacy/data-classes.md) * [Rules](https://docs.ainomos.ch/knowledge/rules.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.