> 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/workspace/admin-notifications.md).
# Manage admin notifications
Configure your personal admin notifications in Siit, including new request, assignment update and SLA alerts filtered by your assignment criteria, and the activity notifications
As a Siit admin, you can configure your **notification preferences** to stay informed about what matters most to you.
Notifications are split into two categories: **General notifications** and **Activity notifications**.
Our notifications are **personal** and must be configured at the individual level in your admin dashboard.
**General Notifications**
General notifications define **how admins are notified about request activity** (creation, assignment, SLA alerts, etc.).
The first three notifications can be customized at different levels:
1. **New request created:** receive a notification when a new request is created and and matches. **your selected assignment criteria.**
2. **Request assignment update:** receive a notification when an existing request's assignment is updated and matches your selected assignment criteria.
3. **SLA alerts:** receive a notification for services with SLA alerts set on requests assigned within your defined scope. SLA alerts are set per service in the service catalog.
Each of these can be set for:
* **Me (yourself)**
* **My inbox**
* **Unassigned requests**
This is a multi-select field, so you can choose several at once.
The two other notifications are per default set to yourself:
* **Mentioned**: receive a notification when you are mentioned on a message or a private note
* **Snooze triggered expired:** receive a notification when a snooze you triggered expires.
⚠️ Notes:
* SLA alerts are only available if SLAs are defined at the **service level** (Pro plan).
* Notifications are only sent after the system checks first the **service assignment rules** and then the **workflows** to make sure they reach the right person.
* You will **not** be notified if you are the author of the action (e.g. if you assign a request to yourself).
**Typical Notification Setups**
Here are common configurations based on admin role and scope:
**Account Owner (overview, not operational)**
* New request created → **Me**
* Request assignment update → **Me**
* SLA alerts → **None**
**Super Admin (tool master, operational + oversight)**
* New request created → **Me & Unassigned**
* Request assignment update → **Me**
* SLA alerts → **Me**
**Manager (team-level visibility + operational scope)**
* New request created → **Me & Inbox**
* Request assignment update → **Me**
* SLA alerts → **Me & Inbox**
**Agent (focus on own tasks only)**
* New request created → **Me**
* Request assignment update → **Me**
* SLA alerts → **Me**
---
# 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/workspace/admin-notifications.md?ask=&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.
