> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/get-started/security/notifications.md).

# Notifications

Manage email notification preferences for your Anedot login. Settings are user-specific and can only be managed by the account holder (the signed-in user).

Manage email notification preferences for your Anedot login. Settings are **user-specific** and can only be managed by the account holder (the signed-in user).

## Update Notification Settings

1. Open the profile dropdown in the upper right corner.
2. Select **Notification Settings**.
3. In **Email Notification Settings**, open the dropdown.
4. Choose **Adjust/Overwrite All Accounts** or select a specific account.
5. Customize preferences.
6. Click **Save**.

## Notification Options

| Notification                          | Description                                                                                                                                       |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| New donation received                 | Alerts you when a donation is successfully processed                                                                                              |
| Minimum in dollars                    | Only alert for donations above a set amount (example: $250)                                                                                       |
| Donation receipt copy (BCC)           | Sends you a copy of each donor’s receipt (off by default; may cause duplicate emails)                                                             |
| Refund, Void, Reversal, or Chargeback | Notifies you if a donation is refunded, voided, reversed (ACH), or charged back                                                                   |
| Chargeback reversal                   | Alert when a chargeback is successfully reversed                                                                                                  |
| Expiring soon                         | Payment method about to expire (donors are also notified)                                                                                         |
| Failed to process                     | Recurring gift failed (donors are also notified and can update payment info)                                                                      |
| Cancelled                             | Recurring gift canceled or deactivated (donors can also reactivate)                                                                               |
| Integration or Webhook Failed         | Failed webhook/integration attempts (off by default; includes error details)                                                                      |
| Transfer received                     | Notifies Admins and Super Admins when a payout is issued. **Not available for** [**custom Permission Sets**](/settings/access/permission-sets.md) |

## After A Failed to Process Notification

When you receive **Failed to process**, find the commitment and help the donor update payment. See [Failed commitments](/finance/management-and-reporting/commitments/failed-commitments.md).

Donors can update payment in the Donor Portal. See [My recurring gift failed, update payment](/donor-support/faq/my-recurring-gift-failed-update-payment.md).

## Not Receiving Notifications?

1. Check spam or junk.
2. Add `info@anedot.com`, `app@anedot.com`, and `help@anedot.com` to your contacts.
3. Whitelist Anedot’s domain with a Gmail filter:

**How to whitelist in Gmail**

1. Open Settings (gear) → Filters.
2. Click **Create a new filter**.
3. In **From**, enter `@anedot.com`.
4. Click **Create filter with this search**.
5. Check **Never send it to spam**, then **Create filter**.

## Related

* [Commitments](/finance/management-and-reporting/commitments.md)
* [Failed commitments](/finance/management-and-reporting/commitments/failed-commitments.md)
* [Account Security Updates](/get-started/security/account-security-updates.md)
* [Users](/settings/access/users.md)
* [Permission Sets](/settings/access/permission-sets.md)
* [Payouts](/finance/management-and-reporting/payouts.md)
* [Refunds and Voids](/finance/management-and-reporting/transactions/refunds-and-voids.md)


---

# 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.anedot.com/get-started/security/notifications.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.