> For the complete documentation index, see [llms.txt](https://support.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.xplorpay.com/resources/notification-management.md).
# Notification Management
Route dispute notifications to one or more e-mail addresses.
## Notification Management
Merchant admins can choose where system-generated notifications are sent.
Route notifications to any e-mail address. This includes distribution lists and external recipients. Recipients do not need to be registered system users.
### Access Notification Management
{% hint style="warning" %}
Notification Management is available to users with the **MerchantAdmin** role.
{% endhint %}
1. In Merchant Portal, select **Account Settings** in the left navigation.
2. Select **Notification Management**.
### Add notification recipients
Each notification type has a recipient field. You can add one or more e-mail addresses.
1. Enter an e-mail address.
2. Press **Enter**, **Comma**, or **Tab** to add it.
3. Repeat for each recipient.
4. Select **Save Changes**.
### Edit a notification recipient
1. Select the e-mail address chip.
2. Update the e-mail address.
3. Press **Enter**, **Comma**, or **Tab**.
4. Select **Save Changes**.
### Remove a notification recipient
1. Select **X** on the e-mail address chip.
2. Select **Save Changes**.
### Supported notification types
Notification Management currently supports these dispute notifications:
* **New disputes** — Sent when a new dispute is initiated.
* **Updates on existing disputes** — Sent when an existing dispute changes or progresses.
Additional notification types may be available in future updates.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://support.xplorpay.com/resources/notification-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
