> 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/request-management/assignment.md).

# Assignment

Assignment happens manually and automatically: defaults set per service, inbox distribution rules, workload and working hours, and workflow routing on any condition. Most teams use a mix

Assignment in Siit happens in multiple places, in multiple ways. Some of it is manual — an admin picks up a request or reassigns it on the fly. Some of it is automatic — Siit distributes work based on inbox rules, workload, availability, and working hours. Most teams use a mix of both.

### Where assignment happens

* **In the Service Catalog** — a default inbox or owner is set per service. Every request from that service lands there automatically.
* **In Inbox settings** — the inbox distribution method, exclusions, and routing rules determine how requests spread across team members once they arrive.
* **In Workflows** — requests can be routed to a specific inbox or person based on any condition: service, department, priority, form answers, requester location, and more.
* **In the Request** — any admin can manually reassign the inbox or the assignee from the request sidebar at any time. All changes are logged on the timeline.

### Service-level defaults

Use the Service Catalog to decide where requests should land by default. When an employee selects a service in Slack/Teams or the portal, Siit:

1. Creates the request with your pre-selected inbox or owner
2. Applies the service's SLA policy
3. Runs any related workflows

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FuVGGOYFOwOIiYafwqmQx%2FCleanShot%202025-10-17%20at%2018.07.07.png?alt=media&amp;token=ccadba32-7d65-46db-be3c-94adbc510155" alt=""><figcaption></figcaption></figure>

**Tips:**

* Point repeatable services to a team inbox rather than an individual, then let the inbox method distribute the work.
* For single-owner services (e.g. "Legal review"), assign to a specific person and add a fallback rule in workflows in case they're unavailable.

### Inbox distribution methods

Once a request lands in an inbox, it gets distributed to a member using one of three methods: **Manual** (agents pick up work themselves), **Round-robin** (sequential rotation), or **Balanced** (goes to whoever has the fewest active requests). The method is set per inbox, so different teams can operate differently.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2F7Tv1cvBIL48t4rFvZLIw%2FCleanShot%202025-10-17%20at%2018.08.11.png?alt=media&amp;token=ba10c30a-5f7d-49ba-bb28-2dbb93108ef6" alt=""><figcaption></figcaption></figure>

### Exclusions

Specific admins can be excluded from automatic assignment while keeping full inbox access. Useful for managers who need visibility without a queue, or specialists who only handle escalations — they can still pick up or be assigned work directly.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2F1hRIAW8xNIZ3DRMnWxC2%2FCleanShot%202026-03-23%20at%2017.35.45%402x.png?alt=media&amp;token=18a9d8cc-49d4-4902-8648-3eaa22bcccba" alt=""><figcaption></figcaption></figure>

**When to use this:**

* A team lead or manager who needs inbox visibility but shouldn't carry a request queue
* An admin on a temporary reduced schedule, is off or transitioning between teams
* A specialist who handles only escalations, not first-touch requests

### Routing rules

Three rules give finer control over how requests flow through an inbox automatically:

* **Auto-assign to next available** — when no admin is currently available at the point a request lands, it waits and assigns automatically to the next one who frees up.
* **Max open requests** — caps how many active requests any single admin can hold. New requests skip admins who have hit their limit.
* **Auto-assign unassigned when capacity opens** — when an admin drops below their cap, the next unassigned request in the queue is automatically pulled to them, in a configurable priority order.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FgXs1p0eAVpMlZ4u4Rooz%2FCleanShot%202026-03-23%20at%2017.36.05%402x.png?alt=media&amp;token=684792d7-a64f-48f4-b950-0350aa8e788f" alt=""><figcaption></figcaption></figure>

### Availability-based routing

Admins can be assigned a Business Calendar within an inbox, defining their working hours in that context. Siit routes requests only to admins currently within their calendar's active hours. Because the calendar is set at the inbox level, the same admin can operate on different schedules in different inboxes.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FMWS24O4KUcvSMqy70q0s%2FCleanShot%202026-03-23%20at%2017.36.49%402x.png?alt=media&amp;token=ace25e6c-32e3-4947-811b-d4312cd33612" alt=""><figcaption></figcaption></figure>

**Example:** Your inbox has three admins — one in Paris (CET), one in New York (ET), one in Singapore (SGT), each with their respective Business Calendar assigned. A request arrives at 2pm CET: only the Paris admin is within working hours, so Siit routes to them automatically.

### Workflow-based routing and assignment

For fine-grained control, use the **Assign to** action in a workflow. Combine it with conditions such as:

* **Request data:** service, channel, tags, priority, status
* **Requester attributes:** department, location, employment type, manager
* **Form answers:** app selected, office, device type, urgency

The **Assign to admin** action can also spread the work itself. Under **Assign to**, pick **Specific admin** to always assign the same person, or **Rotate between admins** to give it an ordered list of at least two admins: each run assigns the next one on the list, then starts again at the top. The rotation keeps its place when you publish a new version of the workflow, and starts over when you change the list, reordering it included. There is no availability or workload check here — an admin who is no longer active simply has their turn passed to the next one on the list.

### Manual assignment in a request

From the request sidebar you can:

* **Change Inbox** to move the request between teams. If the destination inbox uses Round-robin or Balanced, Siit auto-assigns to a teammate there.
* **Change Assignee** to a specific person or click "Assign to me."
* **Unassign** when you need the inbox method to pick the next owner.

All changes are logged on the timeline for audit and reporting.

The assignee dropdown shows each admin's current workload before you pick one: an open-Request count sits next to every name, and hovering shows their availability (online or offline, and until when if an end time exists), their email, and their open-request maximum if one is set. Discarded Requests are left out of the count, so it reflects live work only.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FDYBVtUF30rAQN6m6rmnm%2FCleanShot%202026-08-19%20at%2011.41.56%402x.png?alt=media&amp;token=24766126-3a5e-4d69-a74c-b26f1f19f691" alt=""><figcaption></figcaption></figure>

*Related:* [*Business Calendars*](https://docs.siit.io/workspace/business-calendars.md) *·* [*SLAs*](https://docs.siit.io/service-catalog/slas.md) *·* [*Workflows*](https://docs.siit.io/core-platform/images-and-media.md) *–* [*Actions library*](https://docs.siit.io/workflow/actions-library.md)


---

# 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/request-management/assignment.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.
