> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/system/settings/manage-email-notifications.md).

# Manage email notifications

In FinOps for Cloud, you can customize your email notification settings to determine which notifications you want to receive to stay informed about important updates. 

The notifications are organized into various categories, including:

* **FinOps** – This includes weekly expense reports, pool limit alerts, and notifications for new saving opportunities.
* **Policy alerts** – This includes all policy-related alerts.
* **Recommendations** – This includes all savings and security recommendations.
* **System notifications** – This includes system status or operational messages.
* **Account management** – This includes notifications related to account invitations.

### Manage email notifications

To manage your email notifications:

1. Navigate to the **Settings** page, then select the **Email notifications** tab.
2. Select the arrow next to each category to expand it and view the individual notification types. A list of alerts appears, along with toggle switches to enable or disable them.
3. Use the toggle button to manage your preferences:
   * Purple (On) – You will receive email notifications.
   * Gray (Off) – You won't receive email notifications.

At the top of each category, a label shows how many alerts are active out of the total available (for example, **Active: 4/4**). 


---

# 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.finops.softwareone.com/system/settings/manage-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.