> 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.md).
# Alarm Center
Alarms notify you about system-level issues and errors in your cloud environments, and license management. These are notifications about the system failures on Prisma Cloud and are not related to Alerts. After you enable Alarms, Prisma Cloud automatically generates alarms related to external Integrations status, onboarded Cloud Accounts status, and license management that includes license usage and expiry, and when credit usage exceeds a configured threshold.
You can enable or disable Alarm Center on [Enterprise Settings](/content-collections/administration/define-prisma-cloud-enterprise-settings.md).
Prisma Cloud administrators with the System Admin role have full access to all Alarm Center functionalities. Account Group Admins can only log in, review alarms, and view the notification details. Account Group Admins can contact their Prisma Cloud System Admin to create notification rules.
In addition to enabling Alarms, you can also:
* [Review](/content-collections/administration/alarm-center/review-alarms.md#idc3a681e6-0fef-4c8d-b22e-78f988e2634c) Alarms and take necessary action to resolve them.
* Set up [notifications](/content-collections/administration/alarm-center/set-up-email-notifications-for-alarms.md#id264d726e-6980-4d24-8508-00d5a5d7196a) for Alarms.
---
# 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.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.
