> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/reference-and-developer-docs/role-based-access-control/configuration-permissions/alert-notifications-permissions.md).

# Alert Notifications permissions

Configure permissions for alert notifications.

Controls access to configure notification rules, templates, and external integration forwarding.:

* Configurations: Manage rules through **Settings** → **Configuration** → **General** → **Notifications**: Includes main notification rules and user notifications.
* External forwarding: Configure through **Settings** → **Configuration** → **Integrations** → **External Applications**.

{% hint style="warning" %}

### Caution

Configuring alert notifications requires underlying infrastructure. If forwarding notifications via Syslog, users need access to the Broker Service. For Slack or Email, users need access to the Integrations permissions.
{% endhint %}

| Permission | Description                                                        | Roles Example                                                                                                                                                                                                                                 |
| ---------- | ------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None       | No access to notification configuration.                           | <ul><li>SOC Tier-1 or SOC Tier-2 Analyst: Typically don't need to configure notifications or check notification forwarding destinations.</li><li>Threat Hunter: Notification configuration is not typically part of threat hunting.</li></ul> |
| View       | Read-only access to notification settings.                         | <ul><li>SOC Tier-3 Analyst: May review notification forwarding.</li></ul>                                                                                                                                                                     |
| View/Edit  | Full access to create, modify, and delete notification forwarding. | Security Engineer: Often responsible for configuring notification integrations.                                                                                                                                                               |

### Required and recommended permissions

Consider adding the following permissions:

| Permission     | Permission Level  | Reason                                                                                                                                                              |
| -------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cases & Issues | View              | Notifications can be configured for case-related events; understanding case workflow is essential. Strongly recommended.                                            |
| Broker Service | View or View/Edit | <ul><li>View: Required if using Broker VM for Syslog forwarding of notifications.</li><li>View/Edit: Configure Broker-based Syslog notification channels.</li></ul> |
| Integrations   | View              | Provides visibility into integration health. Consider View/Edit to configure new integration instances used by notification channels. Strongly recommended.         |
| Query Center   | View              | Query notification-related data and troubleshoot notification delivery. Recommended.                                                                                |
| Auditing       | View              | Track changes to notification configurations for compliance. Recommended.                                                                                           |
| Dashboards     | Enabled           | View notification-related dashboards and delivery metrics. Recommended.                                                                                             |


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/reference-and-developer-docs/role-based-access-control/configuration-permissions/alert-notifications-permissions.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.