> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/settings-and-plans/notifications.md).

# Email notifications

Receive an email when a task finishes updating or reverting products.

1. Open **Settings** in the app menu.
2. Under **Notifications**, tick **Automatically send notifications when a task is updated**.
3. In **Emails**, enter the addresses that should receive the messages, separated by commas (up to five). Leave the box empty to use your Shopify store email.
4. Click **Save**.

## When you receive an email

The app sends an email in two situations:

* a task has finished **updating** products;
* a task has finished **reverting** products.

The email is sent about 10 minutes after the task finishes. It contains the task name, how many products were updated or reverted, the product selection and the editing rules, and a **View history** button that opens the task details page.

No emails are sent when a task starts, pauses or fails. Check the Tasks list or the task details page for those states.

{% hint style="info" %}
The email you enter when exporting a large product change list is separate from this setting. See [Export product changes](/bulk-price-editor-sami/manage-tasks/export.md).
{% endhint %}


---

# 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.samita.io/bulk-price-editor-sami/settings-and-plans/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.