> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/advertiser-team-and-user-management/managing-email-notifications.md).

# Managing email notifications

Manage which recipients receive email notifications for your team.

Notification emails use your retailer's branding in addition to Epsilon's and are sent in your namespace's default language.

To enable notifications: go to Teams → \[team name] → Email Notifications, turn on the notification types you need, and add subscriber email addresses.

This page covers team-level email notifications. For the full overview of in-UI and email alerts, see [Platform Notifications](https://help.citrusad.com/retail-media-interface/platform-navigation/platform-notifications.md).

### Manage email notifications

1. Go to **Settings → Teams**.
2. Select your team.
3. Open **Email Notifications**.
4. Enable or disable the notification types your team receives:
   * **Campaign approval** — Emailed when a campaign is approved.
   * **Campaign rejection** — Emailed when a campaign is rejected.
   * **Low wallet balance** — Emailed when a wallet drops below a set threshold.
5. For low wallet balance notifications, set the balance threshold and reminder frequency.
6. Use the recipient table to see who is currently receiving notifications.
7. Open the action menu on a recipient to edit their preferences or stop sending them notifications.
8. Select **Add recipients** to add a team member or a custom email address, such as a finance contact for wallet balance alerts.
9. Choose which notification types that recipient should receive.

### How recipients work

You can send email notifications to:

* Team members already in the platform
* Custom email addresses outside the platform

Available notification types depend on your retailer's configuration, so your team may not see every option listed above.

#### Guided tour

Take a guided tour below to see step-by-step how easy it is:

{% embed url="<https://epsilon.storylane.io/share/ykk73sz84jgy>" %}


---

# 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://help.citrusad.com/retail-media-interface/advertiser-team-and-user-management/managing-email-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.
