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

# Notifications

Choose which render updates you receive and whether they appear in the app, on your desktop, or by email.

Click your name or account icon at the bottom of the sidebar, then open **Notifications**.

## Choose your updates

The list shows the updates available for your account:

| Update              | When it appears                                                                                                       |
| ------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Job complete**    | A job has finished rendering. Some frames may still need your [approval](/docs/web-app/review-and-approve-frames.md). |
| **Scene processed** | An uploaded scene has finished processing and is ready to use when [creating a job](/docs/web-app/create-a-job.md).   |

Use the checkbox beside an update to turn its notifications on or off, then select **In-app**, **Desktop**, or **E-mail** for that row. You can use more than one.

Changes save automatically. Turning off an update disables its **In-app**, **Desktop**, and **E-mail** options. Unchecking all three options also turns off notifications for that update.

{% hint style="info" %}
Keep the web app open to receive in-app and desktop updates. Completed work does not trigger a notification when you return.
{% endhint %}

## Try a notification

Click **Demo** under **In-app** or **Desktop** to check how a notification appears. For desktop notifications, allow the browser's permission request if it appears.

If a desktop notification cannot be delivered, read the warning in the app. It explains whether notifications are blocked or unavailable. See [Browser support](/docs/help/browser-support.md) for browser and system notification settings.

**Demo** under **E-mail** requests a test email. If it is unavailable, the app shows **Demo email unavailable**. After a successful request, the button shows a countdown before another can be requested.

## Messages that always appear

Errors and feedback about actions you take, such as a failed request, still appear inside the app even when account notifications are turned off.


---

# 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://know.rendernetwork.com/docs/web-app/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.
