> ## Documentation Index
> Fetch the complete documentation index at: https://raindrop.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> What Raindrop sends to Slack and email, and how to route it

Raindrop pushes its findings to you so you hear about problems without watching the dashboard. Everything is managed per project at [Settings → Notifications](https://app.raindrop.ai/settings/alerts).

There are four kinds:

* **[Issues](/docs/platform/issues.md)**: a new detected issue, sent automatically when Issue Detection finds one.
* **[Stumbles](/docs/platform/issues.md#stumbles)**: a single conversation where something went wrong, sent automatically as it's flagged.
* **[Signal Alerts](/docs/platform/signal-alerts.md)**: real-time alerts when a signal crosses a threshold you set.
* **[Briefs](/docs/platform/briefs.md)**: written reports. The Daily Digest, custom briefs, and Change Reports.

## Delivery

Each project has a default Slack channel. Issues, Stumbles, Signal Alerts, and Briefs all go there unless an entry overrides it with its own channel. Set the default at the top of Settings → Notifications, along with the timezone used for scheduled briefs.

Issues can also be emailed to you. Email is personal, so turning it on or off only affects your inbox, and each Issue email carries an unsubscribe link for this project or all projects.

## Issues and Stumbles

Turn on **Issue Detection** to get every detected issue, and **Stumbles** to get every flagged conversation. For Issues, set a minimum priority (all, medium and up, high and up, critical only) separately for Slack and for email, so the channel sees everything while your inbox only gets what's urgent.

Stumbles are one-off failures, so they arrive more often than Issues. A Stumble notification links to the flagged conversation with what happened, why it was flagged, and a timeline of the key moments. See [Issues → Stumbles](/docs/platform/issues.md#stumbles) for how they relate to detected issues.

### Routing instructions

Once Issues or Stumbles are on, write plain-English rules for who gets mentioned and what to skip. Type `@` to mention a person or group. For example: "If severity is high, mention @oncall. Skip issues affecting fewer than 3 users. If tagged billing, mention @payments." Raindrop applies the rules to each Issue and Stumble before posting.

## Related

* [Issues](/docs/platform/issues.md) for Issue Detection and Stumbles
* [Signal Alerts](/docs/platform/signal-alerts.md) for threshold alerts on a signal
* [Briefs](/docs/platform/briefs.md) for the Daily Digest, custom briefs, and Change Reports
* [Triage Agent](/docs/platform/triage-agent.md) to set up an alert or brief from Slack


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.