> ## 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.

# Inbox

> Decide what waits for you, follow your own requests, and see what happens to what you submitted.

The **Inbox** collects everything that waits for a person's decision, across every room you can reach: proposals from people, apps and dreaming, exception requests, rules found in documents, access requests and budget requests. You only see items you are allowed to decide, and every decision is recorded as evidence.

Who can do this: everyone has an Inbox. What it holds depends on your responsibilities in each room (owner, decider or curator) and on your platform role. See [Roles](https://docs.ainomos.ch/admin/roles.md).

## Find what waits for you

* **The Inbox icon** at the top right carries the number of open items. Select it for a short list grouped by type, newest first. Select a line to open the Inbox with that item selected, or select **View all**.
* **The chip in the chat.** When items wait in the room you are in, a chip next to the input field says, for example, "3 to decide · in Finance". Select it to open the Inbox for that room.

The count updates when you move to another page or come back to the browser window. Inbox items appear only inside Ainomos; there are no email notifications for them.

## The three views

The switch in the top bar of the Inbox page offers three views, each with its count.

| View | What it shows |
| - | - |
| **To decide** | The items waiting for your decision. |
| **Requests** | Every exception request in your rooms, whoever filed it, with its state. |
| **Submissions** | Knowledge your apps submitted for you, with its state: **Open**, **Accepted** or **Discarded**. Select **Open review** to see it in the import review. |

In **To decide**, the list is on the left and the selected item on the right. The first item is selected when the page opens.

* **Filter** narrows the list by **Type** or by **Rooms with open work**. Each active filter shows as a chip; its × removes it.
* The room picker at the top left starts with **All rooms**. Pick a room to see only its items. When rooms beneath it have items too, tick **Include rooms below** to add them. **Show all rooms** returns to every room.

## What can arrive

| Type | What it is | Who decides | How |
| - | - | - | - |
| **Decision draft** | A new decision proposed by an app, by the chat during a conversation, or from a decision import. | Deciders for that decision type | **Accept** or **Reject** here, or **Open** to read and edit it in **Knowledge** first. |
| **Rule to approve** | A rule found in an imported document. It does not apply until approved. Rules from one document wait as one item. | Room owners | Choose the **Strength** (**Hard**, **Guardrail** or **Convention**), then **Approve** or **Reject**. |
| **Exception request** | A request for a time-limited exception to a guardrail. | Owners of the room where the rule is set | Set **Time limit (days)** and **Reason**, then **Accept** or **Reject**. |
| **Dreaming proposal** | A proposal from [dreaming](https://docs.ainomos.ch/knowledge/dreaming.md), for example a contradiction or a relation between decisions. A relation filed by an app shows as **Relation proposal from** and the app's name. | Curators, or the decider of a decision the proposal would end | **Accept** or **Reject**. A rulebook change asks you to choose one of its options first. |
| **Status change proposal from**, **Relation batch**, imported decisions | Many entries in one proposal. Imported decisions are listed with the decision drafts. | Each entry by its own decider or a curator | Entry by entry, see below. |
| **Knowledge draft** | Knowledge an app submitted for a room, waiting for review. | Curators | **Accept** or **Reject**. Several drafts from one submission open in the import review through **Open**. |
| **Knowledge finding** | A maintenance finding, such as stale knowledge or an expired exception. See [Knowledge health](https://docs.ainomos.ch/knowledge/knowledge-health.md). | Curators | **Mark as resolved** or **Won't fix**. Only the finding's state changes. A finding about an exception also offers **Open exception**. |
| **Agent approval** | An action a connected app or agent wants to take, held until a person approves it. | Room owners | **Accept** or **Reject**. The detail shows the **Call arguments** the action would run with. |
| **Brain access request** | A room owner asks to use protected shared knowledge that another room publishes. | The approvers named for that knowledge | **Accept**, or **Reject** with a reason. |
| **Budget request** | A room owner asks for a higher monthly budget, with a reason. | platform admins | **Accept**, or **Reject** with a reason. Accepting sets the room's budget to the amount requested. |
| **System** | A connected system is down. | platform admins and maintainers | **Open System status**. See [System status](https://docs.ainomos.ch/admin/system-status.md). |

Room owners can also decide every item of their room that the table gives to deciders or curators. Budget requests, brain access requests and system items follow their own roles.

## Decide an item

**1. Select the item**

The right side shows the record itself: its facts, its full text, the records it affects and, for a proposal, **What acceptance does**.

**2. Add a reason where it is asked for**

An exception request needs a **Reason** to accept and to reject. A budget request and a brain access request need one only to reject.

**3. Accept or reject**

A green line confirms the decision and the item leaves the list. After you accept a decision draft, the line names its key, with **Open** to go to it.

For an exception request, **Time limit (days)** must be at least one day. It starts at the end date the request states, or at 14 days. If the rule itself still waits for approval, approve the rule first.

If someone decided the item in the meantime, or you lack the right, the Inbox says so.

> [!NOTE]
>
> Accepting a relation proposal can, in rare cases, leave it in the list with a note that the relation cannot take effect yet. Nothing is lost. Accepting it again later puts it in force.

## Decide many entries at once

You decide entries in bulk inside a proposal that holds many of them: status changes, relation batches and imported decisions. Other items are decided one at a time.

* Tick single entries, or use **Select all I may decide**. For imported decisions you can also select all of one type, and filter by **Type**, **Enters as** and **Only what needs attention**.
* Select **Accept selected** or **Reject selected**. For imported decisions, Ainomos then says what becomes binding and which decisions of the room the selection ends. You can add a **Note (optional)**, then confirm.
* Entries you may not decide are greyed out and name the role they need, such as "needs the curator". The proposal stays in the Inbox until the others have decided their entries.

## What the requester sees afterwards

* **Exception requests.** **Requests** shows each request's state: **Requested**, **Approved**, **Rejected**, **Withdrawn**, **Revoked** or **Expired**. Open one to see who decided, when, and the decision reason. The requester can **Withdraw** a pending request. Owners can **Revoke** an approved exception, which ends it at once. An approved exception ends by itself when its time limit runs out. See [Exceptions](https://docs.ainomos.ch/knowledge/exceptions.md).
* **Knowledge submissions.** **Submissions** shows whether a reviewer accepted or discarded what an app submitted for you.
* **Decision drafts.** The record in **Knowledge** shows its new status.
* **Budget requests.** The room's **Context** drawer shows an open request. Once accepted, the room's budget is the amount requested.

## Related

* [Reading answers](https://docs.ainomos.ch/chat/reading-answers.md)
* [Exceptions](https://docs.ainomos.ch/knowledge/exceptions.md)
* [Dreaming](https://docs.ainomos.ch/knowledge/dreaming.md)
* [Roles](https://docs.ainomos.ch/admin/roles.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.