<!-- Source: https://ccr-cloud.uubright.com/docs/notifications/ -->
# Notifications

Get a notification when a task needs your approval, finishes a turn or fails, then
tap it to open that task. Notifications are optional; everything works without
them.

## Turn on notifications

Notifications need an HTTPS address, such as one from
[Access from your phone](https://ccr-cloud.uubright.com/docs/remote-access/). On iPhone and iPad, first install the
app to your Home Screen and open it from there.

1. Connect to your server.
2. Select **Enable notifications** and allow the browser or system prompt.

To stop them on one device, select **Turn off notifications** there.

## What you'll be notified about

| Event | Notification |
|---|---|
| A task needs approval | **Approval needed: TOOL** |
| Claude finishes a turn | **Turn finished**, with the start of Claude's reply |
| A task fails | **Session failed**, with the task title and reason |

A finished turn means Claude stopped working on your request. It doesn't mean
tests passed.

## Answer from the notification

Where the platform shows notification buttons (Chrome on Android, and Chrome or Edge
on desktop; not iPhone or iPad today), an approval notification has:

- **Deny**, always.
- **Allow once**, only for tools that just read files (Read, Grep, Glob, LS and
  NotebookRead), and only when every path they read is inside the task's workspace.
  A read of anything outside it, such as your home directory or `/etc`, and anything
  that runs commands, edits files or uses the network, has only Deny; tap the
  notification to review it in the app, where the exact input is shown.

A button answers exactly the request in that notification. If the request was already
answered, cancelled or interrupted, or the notification is more than a day old, the
button does nothing and the app opens instead, so an old notification can never
approve something else.

## How delivery works

Each ccr-cloud server has its own push keys and sends notifications directly
through your browser's push service. No ccr-cloud project service is involved. Push
availability depends on the browser and platform; if a notification doesn't arrive,
the app still shows everything.

To check delivery to every registered device, use the HTTP API's
[test route](https://ccr-cloud.uubright.com/docs/api/#notifications). Set `CCR_CLOUD_PUSH_SUBJECT` to your own
`mailto:` or `https:` contact address; push services use it to reach whoever runs
the server, and Apple rejects `localhost` addresses.

## Discord

For notifications in Discord instead, set up [Discord control](https://ccr-cloud.uubright.com/docs/discord/). It sends
direct messages for the same events and lets you answer approvals there.
