> For the complete documentation index, see [llms.txt](https://docs.fulfillmenttools.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fulfillmenttools.com/documentation/backoffice/network-view/notification-center.md).
# Notification center
Backoffice displays alerts through a notification icon in the topbar. The icon includes a badge counter showing the number of alerts remaining in the inbox. Alerts originate from multiple system processes and cover a wide range of operational scenarios across facilities and the network, such as:
* New pick job created
* Upcoming time-triggered reroute
* Routing plan isn't routable
* Routing plan waiting
Alert visibility follows three principles:
* **Tenant- and facility-based visibility:** Only alerts that belong to the user's tenant and assigned facilities are displayed.
* **Global seen and archived state:** When an alert is archived, it's removed from the inbox for all users because the archived state is global.
* **Permission-independent visibility:** Alerts are shown even if the user doesn't have access to the linked detail page. In such cases, the notification remains visible, but there's no link to the relevant section.
More about setting up notifications can be found in the [Notification center article](/documentation/getting-started/eventing/notification-center.md).
## Notification panel
Clicking the notification icon opens a dropdown panel with two tabs, [Inbox](#inbox) and [Archive](#archive). You can close the panel by clicking the **X** icon.
### Inbox
{% columns %}
{% column %}
The **Inbox** tab lists all active alerts from the last 30 days. Each entry displays the:
* Alert type
* Affected entity
* Links to the relevant Backoffice sections
* Priority
* Timestamp
A refresh icon lets you manually refresh the alert list. Otherwise, notifications are updated every two minutes.
The filter icon opens an overlay where you can select **Priority** or **Category** to filter the notifications shown. See the [Filter section of this article](#filter) for more information.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
When hovering over an alert, an archive icon appears if you have the `NOTIFICATION_WRITE` permission. Clicking this moves the notification to the **Archive** tab for all users, not just you. This action can't be undone.
Once a notification has been visible for 30 days, it will be removed automatically, and you'll no longer be able to access it.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### Archive
{% columns %}
{% column %}
The **Archive** tab displays alerts that were archived in the last 30 days by any user. Archiving is a global action, so if you archive a notification, it will be archived for everyone on your team.
You can also filter and refresh in the **Archive** tab.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### Filter
{% columns %}
{% column %}
You can filter notifications in each tab by category and priority, allowing you to refine the list based on operational relevance.
If you set filters in the **Network view**, they will persist until you remove them there. The filters in the **Facility view** are separate, but will also persist until you remove them in the **Facility view**.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### Links in alerts
{% columns %}
{% column %}
Alerts may include links such as **Go to orders** or **Go to facility**. All links appear below the message content.
If the underlying page isn't accessible due to missing permissions, the link isn't displayed.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
---
# 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.fulfillmenttools.com/documentation/backoffice/network-view/notification-center.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.
