> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/admin-inbox-notification-settings-for-transactions.md).

# Admin: Inbox Notification Settings for Transactions

Admins can now customize which transaction inboxes send them email notifications, helping them stay on top of the updates that matter most to them and their role.

{% embed url="<https://rechatq.wistia.com/medias/p20013e4gj/manage>" %}

New **Inbox Notification Settings** are now available within Transactions, allowing admins to:

* Choose which inbox tabs send email alerts
* Reduce unnecessary notification noise
* Stay updated on important transaction activity like commissions and deal updates
* Personalize your notification experience based on your workflow

### How It Works

Within Transactions, admins will now see a new **Inbox Notifications** icon where they can manage notification preferences.

Simply:

1. Navigate to **Transactions**
2. Click the **Inbox Notifications** icon
3. Toggle email notifications on or off for desired inboxes
4. Close the panel to automatically save your preferences

Your settings are saved instantly and can be updated anytime.

{% embed url="<https://studio.saltfish.ai/demo-share/demo_1780343229133_vmhignt7r>" %}


---

# 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.rechat.com/whats-new/admin-inbox-notification-settings-for-transactions.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.