> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/request-management/inboxes-management.md).

# Create and manage inboxes

Create Inboxes to group admins who handle requests together, set manual, round-robin or balanced assignment rules, and attach Inboxes to services for routing

### 👀 Overview of Inboxes

In the internal ticketing management system world, employee requests are typically managed by Admins. In Siit, Admins are users with access to the platform to handle these requests.

To enhance efficiency, especially in organizations with multiple teams and admins, Siit introduces the concept of ***Inboxes***. An Inbox is a group of admins responsible for managing employee requests collectively. This feature allows for efficient request assignment and collaborative resolution.

### 🎯 Key benefits of Inboxes

1. **Assign requests to a group of admins**: distribute workload effectively.
2. **Define intelligent and advanced assignment rules**: use options like manual assignment, round-robin distribution, or balanced allocation.
3. **Enable collaboration within requests**: Admins from a same Inbox can interact, view, and take actions directly inside the request.

**Assign requests to a group of admins**: distribute workload effectively.

**Define intelligent and advanced assignment rules**: use options like manual assignment, round-robin distribution, or balanced allocation.

**Enable collaboration within requests**: Admins from a same Inbox can interact, view, and take actions directly inside the request.

### 🤔 How to configure Inboxes

1. Navigate to **Settings** > **Request Settings**.
2. Select **Inboxes**.
3. Click **Add**.
4. Provide a **Name** and select a **Color** to identify the Inbox.
5. Add the admins who will be part of the Inbox.

Navigate to **Settings** > **Request Settings**.

Select **Inboxes**.

Click **Add**.

Provide a **Name** and select a **Color** to identify the Inbox.

Add the admins who will be part of the Inbox.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-244f015e98f0626e43df294573b29a8c95828395%2FCleanShot-2025-07-16-at-16-05-55-2x-png.png?alt=media" alt=""><figcaption></figcaption></figure>

### Define the advanced Assignment

Once the request is automatically assigned to an inbox, you can decide how this one will be distributed to a specific Admin inside the inbox, following the below options:

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-7a00be697dbba1bc8766b43ae1a368a422986021%2FScreenshot-2024-12-24-at-11_28_57.png?alt=media" alt=""><figcaption></figcaption></figure>

### ✅ Attach Inboxes to Services

Once you’ve created your Inboxes, add them to specific **Services**. This ensures that any request raised for a service is automatically assigned to the appropriate Inbox.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-f16d55696ee42d9196e9fb837cebb183797923a1%2FScreenshot-2024-12-24-at-11_30_06.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/guides/request-management/inboxes-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
