> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/manage-issues/notifications.md).
# Notifications
Soda’s **notification system** helps you stay informed when data issues occur—whether it’s a failed check or an anomaly detected through metric monitoring. Notifications are dynamically dispatched using **Notification Rules**, allowing you to target alerts based on specific properties, attributes, or datasets.
## How Notification Rules work
Notification Rules define **when** and **to whom** a notification is sent. Rules can be configured to match specific checks or anomalies, ensuring the right people are notified at the right time.
## Create a Notification Rule
{% hint style="warning" %}
Only users with the **Manage Notification Rules** permission can create or edit rules. All users can view rules. Read about [Global and Dataset Roles](/organization-and-admin-settings/global-and-dataset-roles.md)
{% endhint %}
To create a new Notification Rule:
{% stepper %}
{% step %}
Click on your profile in Soda Cloud and select **Notification Rules** from the menu.
{% endstep %}
{% step %}
Click **New Rule**.
{% endstep %}
{% step %}
Provide a **name** for the rule.
{% endstep %}
{% step %}
Define the **Rule Scope**.
**Checks**:
* **All checks**: The rule applies to every check in your organization.
* **Specific checks**: Build custom rules by filtering on check properties, dataset properties, or attributes.
{% endstep %}
{% step %}
Define the **recipients** (users, groups, or integrations like Slack, Teams, or webhooks, see [Integrations](/integrations.md)).
{% endstep %}
{% step %}
...and choose the **alert type**: Warn & Fail, Fail, Not Evaluated, Excluded, or all results.
{% endstep %}
{% step %}
\[Optional] **Advanced options**
* Enable **Granular Results** to include column-level details and check results.
* Enable **Personalized Message** to include context for this notification rule.
{% endstep %}
{% step %}
**Save** to create the Notification Rule.
{% endstep %}
{% endstepper %}
***
## Pause Notification Rules
You can **pause a Notification Rule** at any time to temporarily disable alerts without deleting the rule.
***
## Disable legacy agreement notifications
If your organization previously used agreement-level notifications (Soda v3), an organization **admin** can disable them in **Organization Settings** → **Agreement notifications**.
With agreement notifications off, all alerts are dispatched through Notification Rules instead:
***
{% if visitor.claims.plan === 'datasetStandard' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Dataset Standard license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}
{% if visitor.claims.plan === 'enterprise' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Team license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}
{% if visitor.claims.plan === 'enterpriseUserBased' %}
{% hint style="success" %}
You are **logged in to Soda** and seeing the **Enterprise license** documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
{% endhint %}
{% endif %}
{% if !(visitor.claims.plan === 'enterprise' || visitor.claims.plan === 'enterpriseUserBased' || visitor.claims.plan === 'datasetStandard') %}
{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Documentation access & licensing](/reference/documentation-access-and-licensing.md).
If you do have a Soda license, make sure to **log in to Soda Cloud in this same browser**.
{% endhint %}
{% endif %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.soda.io/manage-issues/notifications.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.