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

# About Notifications

> Learn how to configure and manage alerts for data quality issues in Validio.

Notifications in Validio are alerts that inform you about data quality issues and incidents in your sources and validators. These messages provide essential context for incident triage:

* Incident severity levels
* Incident priority
* Source owner, tagged directly in the message on Slack and Microsoft Teams channels when the notification rule opts in
* Affected data sources
* Segmentation details
* Metric graphs showing deviation patterns and alert triggers

![The new notification channel form, with the default notification rule configured alongside it](https://mintcdn.com/validio/36lh-6_uXUsulPvT/images/docs/notifications/900-channel-new.png?fit=max\&auto=format\&n=36lh-6_uXUsulPvT\&q=85\&s=b5885d71a00ec63f60eebda0bf8dc413)

Notification channel and default rule configuration

## How notifications work

Validio notifications are configured across three resources: integrations, channels, and rules.

### Integrations

**Integrations** store the connection and credentials for an external service such as a Slack workspace, a Jira instance, or an SMTP server. You configure an integration once at **Workspace > Integrations** and then reuse it across any number of channels. For more information, see [Managing Integrations](https://docs.validio.io/v11.1/docs/access-and-settings/settings/managing-integrations.md).

### Notification channels

**Notification channels** reference an integration and add the destination details, such as a specific Slack channel ID, a Jira project key, or recipient email addresses. Channels route alerts to your team's communication platforms. For supported channels and configuration details, see [Notification Channels](https://docs.validio.io/v11.1/docs/integrations/notification-channels.md).

### Notification rules

**Notification rules** live inside a channel and identify the events that should trigger an alert on that channel. Rules:

* Reference specific conditions that determine when alerts trigger.
* Group incidents by validator to reduce alert fatigue.
* Send consolidated notifications to the channel that owns the rule.
* Optionally tag the incident owner in the message, on Slack and Microsoft Teams channels. See [Adding Notification Rules](https://docs.validio.io/v11.1/docs/notifications/notification-rules.md).

You create and manage rules from each channel's details page. For detailed setup instructions, see [Adding Notification Rules](https://docs.validio.io/v11.1/docs/notifications/notification-rules.md).

## Channel details page

![A notification channel details page listing the rules configured on the channel](https://mintcdn.com/validio/36lh-6_uXUsulPvT/images/docs/notifications/900-channel-details.png?fit=max\&auto=format\&n=36lh-6_uXUsulPvT\&q=85\&s=417687c1d4c41d1e5663767d39720f57)

Channel details page with notification rules

Open a channel by navigating to **Notifications > Channels** and clicking its name. The channel details page shows:

* A **Summary** with the channel's type, integration, namespace, and timestamps.
* A **Notification rules** list, where you can add new rules, edit their conditions, or remove them.
* A **Delivery feed** that shows recent notifications delivered through this channel, so you can verify that alerts are reaching the intended destination.

## Interactive notification messages

![A Validio incident notification in Slack, showing the metric graph and the action buttons on the message](https://mintcdn.com/validio/36lh-6_uXUsulPvT/images/docs/notifications/slack-notification-message.png?fit=max\&auto=format\&n=36lh-6_uXUsulPvT\&q=85\&s=529228a5d31473ac0fe6ac1263855511)

Slack notification message with metric graph and actions

When you enable **Interactive messages** on an integration, you can manage incidents directly from notification messages. Available actions include:

* **Update incident status** — Resolve the incident or provide feedback to improve the anomaly detection model.
* **Assign ownership** — Designate team members to resolve issues.
* **Mute incidents** — Suppress future notifications for specific issues.
* **Add comments** — Document investigation progress for team visibility.

> [!NOTE]
>
> Interactive message features vary by channel, with some platforms offering more options than others.