> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/administration/alarm-center/set-up-email-notifications-for-alarms.md).

# Set Up Notifications for Alarms

Alarm **Settings** allow you to create notification rules to receive notifications via Email, Splunk, Webhook, Google Cloud Security Command Center (CSCC), and PagerDuty channels about the alarms generated when you are away from the Prisma Cloud console.

1. On **Alarm Center** select **Settings**.

   <figure><img src="https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-f4abea7553871f5aca7eae21151142e391a47e6e%2Falarm-center-1-3.png?alt=media" alt="alarm center 1 3"><figcaption></figcaption></figure>
2. Select **Create Notification Rule**.
3. Enter **Rule Name** and select **Alarm Type** (All, Integration, Cloud Account, or License) and **Severity** (High, Medium, or Low), to notify users on the generation of alarms based on the conditions you select.

   <figure><img src="https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-337c3ec7fa46899e344597f5bcdb0acfe81f0021%2Falarms-notification-rule-3.png?alt=media" alt="alarms notification rule 3"><figcaption></figcaption></figure>
4. **Next**
5. Enter **Email Addresses** and select from the available **Channel** types. You have to provide at least one email address and create an email notification rule when you select **Integration** as the alarm type.

   <figure><img src="https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-e85d4554f2ec2725e0b086d2e762e18781df8a9b%2Falarms-notification-rule-4-1.png?alt=media" alt="alarms notification rule 4 1"><figcaption></figcaption></figure>
6. **Next**
7. Review the Notification Rule summary and **Submit**.

   <figure><img src="https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-a010fd04d62ef28fc66d3900ecf21d2f8cc04964%2Falarms-notification-rule-5.png?alt=media" alt="alarms notification rule 5"><figcaption></figcaption></figure>
8. The Notification Rule you created displays under **Alarm Center > Settings**.
9. Use the toggle button to disable any Notification Rule.
10. You can clone, edit, and delete an existing Notification Rule.

    After you save the notification rule, an email will be sent to the email addresses you’ve listed in the rule. Those users can take action on the alarm notification by navigating from the email.

    After you create or update a rule it may take 10 minutes to receive the email notification.


---

# 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.prismacloud.io/content-collections/administration/alarm-center/set-up-email-notifications-for-alarms.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.
