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

# Alerts and notifications

> How an incident becomes an alert: the organization's rules, each person's preferences and the channels.

Every incident event (**New drop**, **Drop got worse**, **Back to normal**) can become an alert. Two layers decide who receives it and where: the **organization's rules**, set by Owners and Administrators, and **each person's preferences**. Webhooks have a filter of their own. This page explains how the layers combine.

## How it works

### 1. Organization rules

Set in **Control Center > Alerts** (see [Control Center](https://docs.usestealth.dev/en/screens/control-center.md)):

* **Events**: which of the three events become alerts. Default: all three.
* **Minimum severity**: drops below it do not become alerts for anyone. Default: **Light** (everything).
* **Exceptions**: mute, or set another minimum severity, for one network, client, format or ad unit, with or without an expiry. The most specific exception wins.
* **Mandatory**: from which severity members cannot turn alerts off. Default: **Critical only**.

An event that does not pass these rules reaches nobody, not even webhooks.

### 2. Each person's preferences

Every member of the organization, whatever the role, receives the alerts that pass the rules, filtered by their own choices in **Settings > Notifications** (see [Email and in-app notifications](https://docs.usestealth.dev/en/alerts/email-and-in-app.md)):

* **In-app notifications** and **Email notifications**, on or off.
* **Minimum severity**: can only narrow what the organization sends.
* **Email frequency**: **Right away** or **Daily summary at 8 AM**.
* **Back to normal**: whether to hear when a drop ends.

**Mandatory** alerts ignore the personal minimum severity. The person still chooses the channel, and the last channel that is on cannot be turned off. If both channels are off, mandatory alerts still arrive in the app.

### 3. Webhooks

Each [webhook](https://docs.usestealth.dev/en/alerts/webhooks.md) receives the events that pass the organization's rules and its own filter (minimum severity and events), right after each check. Webhooks never wait for the daily summary and do not depend on anyone's preferences.

### Notices that bypass the rules

Some notices are about the service itself, not about revenue. They go to every member, in the app and by email, regardless of rules and preferences:

* **Connection revoked**: Google Ad Manager access was removed. Owners and Administrators get the link to reconnect.
* **No recent data**: Stealth could not read a network's Google Ad Manager reports for more than 3 hours. Sent once until the network recovers.
* **Webhook paused**: a webhook was paused after 24 hours of failures.

> [!NOTE]
>
> While an organization is suspended or cancelled, Stealth keeps collecting data and following incidents, but sends no alert, notice, daily summary or webhook.

## What you see

| Where | What arrives |
| - | - |
| The bell in the dashboard | Each alert that passes your filters, right after the check. |
| Email, right away | One email per check with all your new alerts of severity **Critical** (always) and **Attention** (with **Right away**). |
| Email, daily summary | At 08:00 in the organization's time zone, the **Attention** and **Light** alerts since the previous summary, when you chose **Daily summary at 8 AM**. |
| Webhooks | Each event, one request per event, right after the check. |

## FAQ

> [accordion] Can a member stop receiving Critical alerts?
>
> Not while **Critical** is mandatory (the default). They can choose whether those alerts arrive by email, in the app or both.

> [accordion] Is there Slack, Microsoft Teams or Discord integration?
>
> Not directly. Use a [webhook](https://docs.usestealth.dev/en/alerts/webhooks.md) and forward the events from your own system or an automation tool that receives webhooks.

> [accordion] Is there a quiet period at night?
>
> No. To silence alerts for a while, create an exception with **Mute** and a **Duration** of **24 hours**, **7 days** or **Until a date**.


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