> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/guard/features/notification-center.md).
# Notification Center
## Overview
The Notification Center is your in-app inbox for Guard alerts. Notifications arrive when:
* An **Authorization Policy** you are subscribed to detects a deviation.
* A **Drift Policy** triggers after detecting a meaningful change in your security posture.
* A **Real-Time Change Notification** (Change Monitoring Policy) fires based on a rule you or your team configured.
Notifications appear on the bell icon in the Guard header. Clicking “See Inbox” takes you to your personal inbox.
## Your Inbox
Notifications are sorted by the trigger date (most recent first).
Each notification shows:
* The **source feature** (for example: Authorization Policies, Drift Policies, Change Monitoring)
* The **Salesforce org** involved, where applicable
* The **time** the notification was generated
Clicking a notification takes you to the relevant policy in Guard where you can investigate further.
Guard Admins can see all notifications across the platform, not just those that they are assigned to. Select **All Notifications** in the toggle under the inbox to move to this view.
## Archive
Notifications that are no longer needed can be archived. Archiving removes them from your main inbox without deleting them, so you can still refer back to them if needed.
To archive a notification, use the archive action on the notification item.
Archived notifications are accessible from the **Archive** tab in the notification panel.
## **Retention**
Notifications are kept for a total of 90 days before they are automatically removed.
## Notification Groups
Notification Groups let you define named sets of Guard users who should receive notifications from a particular source or policy. Instead of adding recipients one by one each time you create a policy, you create a group once and add it to the recipients list for any notification across Guard.
Only Admins can create, edit or delete Notification Groups.
### **Create a notification group**
1. Open the Notification Settings from the bell icon at the top of the page.
2. Click **Create Notification Group**.
3. Enter a name for the group.
4. Add the Guard users who should be members.
5. Save.
The group is now available as a recipient option when configuring any policy notification.
### **Edit and delete groups**
Open an existing group to rename it, add or remove members, or delete it. Deleting a group does not delete the policies that reference it, but may result in these policies having no recipients.
## Where Notifications Come From
The Notification Center currently receives in-app notifications from these Guard features:
| Source | When a notification is sent |
| ---------------------------------------------------------------------- | ------------------------------------------------------------- |
| Authorization Policies | A policy detects a user or permission set deviation |
| Drift Policies | A daily evaluation finds drift above the configured threshold |
| Real-time Change Notifications (renamed to Change Monitoring Policies) | A monitored metadata change matches a configured rule |
Each source controls who receives its notifications through the recipient settings in the policy rule. You can select individual Guard users or Notification Groups (or both) as recipients.
{% hint style="info" %}
If you were previously receiving email notifications from these features, those emails will continue as before. In-app notifications are delivered in addition to email.
{% endhint %}
## Role-Based Access
All Guard users can view notifications in their personal inbox and archive them.
Only **Admins** can create, edit and delete Notification Groups.
---
# 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://knowledgebase.autorabit.com/product-guides/guard/features/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.
