> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/devices/alerts-and-notifications/alert-administration.md).
# Alert administration
Manage alert subscriptions and control how alert rules behave.
Use **Alert administration** to manage alert subscriptions and configuration.
### When to use this page
Use this page when you need to change who receives alerts or how alert rules behave.
Use it after you identify unwanted noise, missing alerts, or alert thresholds that need adjustment.
### Before you start
Confirm that you know:
* whether you need to change subscriptions or rule behavior
* which alert types need the update
* whether the change should affect delivery, severity, or threshold handling
### Choose the correct change
* Change **subscriptions** when the recipient or delivery preference is wrong.
* Change **configuration** when the alert's severity, threshold, or behavior is wrong.
Subscription changes do not change alert rules. Configuration changes do not add recipients.
### Manage subscriptions
1. Go to **Verifone Central** → **Administration** → **Alerts** → **Manage Subscription**.
Use this page to choose which alerts you want to receive.
2. Select the subscriptions you need.
3. Save the changes.
### Manage alert configuration
1. Go to **Verifone Central** → **Administration** → **Alerts** → **Manage Configuration**.
Use this page to configure:
* severity
* status
* threshold
* automatic close
* always generate new alert
2. Update the required alert settings.
3. Save the configuration.
### Review the impact
Before you save, confirm the alert type and intended outcome. For configuration changes, record the current setting and the new setting.
After saving, review future alert behavior before making another adjustment. Avoid changing several rule settings at once when investigating alert noise.
### Verify the result
After you save the changes, confirm that:
* the right subscriptions are enabled
* the alert rule settings reflect the intended severity or threshold behavior
* future alerts now follow the updated delivery or configuration path
### Result
You can control who receives alerts and how alert rules behave, without confusing delivery changes with rule changes.
### Next steps
* [Alerts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/alerts-and-notifications/alerts) — review live alert entries
* [Alerts and notifications](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/alerts-and-notifications) — return to the alert center
---
# 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.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/devices/alerts-and-notifications/alert-administration.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.
