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

# Data alert settings

> Turn individual data alerts on or off and set each one's severity — Information or Critical.

## What this page is for

This is the **configuration** screen for data alerts — where you decide which alerts you want and how loudly they speak. It is separate from the [Data alerts view](/guide/home/data-alerts), which is the list of alerts that have actually fired. Here you set the rules; there you read the results.

For each alert you do two things: switch it **on or off**, and mark it **Information** or **Critical**. Your changes take effect on the next data sync, so an alert you turn on shows up once fresh data comes in.

**This page has no numeric thresholds.** It only enables alerts and sets their severity. If you're looking to set sales-deviation thresholds — how far actual sales can drift from the forecast before an alert triggers — those live separately in the [Baseline forecast](/guide/demand-planning/baseline-forecast) area, not here.

## What you can set

| Setting            | What it means                                                                                                                                           |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **On / off**       | Whether the alert is active. Off means it never fires.                                                                                                  |
| **Severity**       | **Information** (worth noting) or **Critical** (needs attention). Severity only changes how the alert is flagged — it does not change what triggers it. |
| **Reset settings** | A button that restores every alert to its default on/off and severity.                                                                                  |

## The alert catalog

Alerts are organized into groups so you can find related ones together:

| Group                                 | Example alerts                                                             |
| ------------------------------------- | -------------------------------------------------------------------------- |
| **Network alerts**                    | A warehouse with no incoming connection, so nothing can replenish it.      |
| **Product "invisible assets" alerts** | A product with no safety stock set, so it has no buffer to defend.         |
| **Product lifecycle / setup alerts**  | A product with no assignee, or missing key setup before it can be planned. |
| **Order-risk alerts**                 | An order at risk of arriving late.                                         |

## How it affects planning

These settings shape your **signal-to-noise**. Turning an alert on surfaces a class of data problems you want to catch; turning it off silences noise you've decided not to chase. Severity helps you triage — mark the ones that can stop the plan as **Critical** and the rest as **Information**, so the [Data alerts view](/guide/home/data-alerts) sorts the urgent from the merely informative.

## Step by step: tune your alerts

1. Scan the catalog and turn **off** any alert you don't want to act on.
2. Turn **on** the checks that matter for your process (for example, products with no safety stock).
3. Set each active alert's severity to **Information** or **Critical**.
4. Wait for the next data sync — your changes apply then.
5. Review what fired in the [Data alerts view](/guide/home/data-alerts).

## Example

Your team keeps missing warehouses that can't be replenished. You turn the **warehouse with no incoming connection** alert on and mark it **Critical**. You also switch the **product with no assignee** alert on but leave it **Information**, since it's a cleanup task rather than a blocker. After the next sync, both appear in the alerts view, with the critical one flagged for attention.

> **Note:** If you ever lose track of what you've changed, **Reset settings** puts every alert back to its default. To confirm your data is even flowing in, check [Integrations](/integrations).