> For the complete documentation index, see [llms.txt](https://layerlabs.gitbook.io/abuse-manager-pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://layerlabs.gitbook.io/abuse-manager-pro/optional-and-advanced/override-staff-notifications.md).

# Override Staff Notifications

{% hint style="danger" %}
All members of staff will no longer get automated notifications if you enable the override option. You will have to manually configure this using the new notifications system within WHMCS using the steps below.
{% endhint %}

To override staff notifications:

1. Go to the module settings page
2. Enable the override staff notifications option
3. Go to system settings
4. Click on notifications
5. Click on Create New Notification Rule button
6. Give the notification rule a name
7. Choose API event
8. Click on Custom API Trigger
9. Under Trigger Identifier choose exact match and type one of the options from the table below
10. Choose the required notification settings as per your requirements

| Trigger                | Description                                                                  |
| ---------------------- | ---------------------------------------------------------------------------- |
| amp.staff.queuedabuse  | This trigger is fired when a new abuse report is queued for admin moderation |
| amp.client.reply       | This trigger is fired when a client adds a reply to an open abuse report     |
| amp.staff.reply        | This trigger is fired when an admin adds a reply to an open abuse report     |
| amp.staff.autoassigned | This trigger is fired when a new abuse report is auto assigned               |

Example:

![Creating New Notification Rule for Slack](/files/hD68zLnv6CZYBPY8fiUb)


---

# 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://layerlabs.gitbook.io/abuse-manager-pro/optional-and-advanced/override-staff-notifications.md?ask=<question>&goal=<endgoal>
```

`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.