> ## 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.

# Adding Notification Rules

> Learn how to configure conditions on a channel to trigger alerts in Validio.

Notification rules define the conditions that trigger alerts in Validio and live inside a [notification channel](https://docs.validio.io/v10.1/docs/integrations/notification-channels.md). Open the channel's details page to create rules, edit their conditions, and see which incidents have triggered them.

![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)

Notification rules on a channel details page

Each rule belongs to exactly one channel. You view and manage a channel's rules from the **Notification rules** section of its details page. Each rule renders as a card with its name and a row of condition chips — **Source**, **Type**, **Severity**, **Priority**, **Segment**, **Owner**, and **Tags**. Click any chip to set its value; empty chips show **Any source**, **Any type**, **Any severity**, **Any priority**, **Any segment**, **Any owner**, or **Any tags**. Click **Save** to apply your changes, or **Cancel** to discard them. Use the ⋮ menu next to each rule to **Rename** or **Delete** the rule.

## Add a new rule

![The new notification rule form, with the condition types available for the rule](https://mintcdn.com/validio/36lh-6_uXUsulPvT/images/docs/notifications/900-rules-new.png?fit=max\&auto=format\&n=36lh-6_uXUsulPvT\&q=85\&s=2fd07d94dd1d85ab7b66860e7c32b0c3)

New notification rule configuration

Follow these steps to create a new notification rule on a channel.

1. In Validio, navigate to **Notifications > Channels** and click the channel that should receive the alerts.
2. In the **Notification rules** section, click **+ New notification rule**.
3. Enter a descriptive **Name** for the rule, such as "High severity production incidents".
4. In the same dialog, set at least one condition chip (**Source**, **Type**, **Severity**, **Priority**, **Segment**, **Owner**, or **Tags**). Click **+ Add tag condition** or **+ Add segment condition** to add another tag or segment chip after the first one has a value. See [Configuration Options for Conditions](#configuration-options-for-conditions) for the supported condition types.
5. Click **Create**. The button stays disabled until the rule has a name and at least one condition.

> [!NOTE]
>
> A notification rule requires at least one condition. Use the chips to narrow the rule to the incidents you care about — for example, set the **Severity** chip to `High` and `Critical` to alert only on serious incidents.

## Configuration options for conditions

Conditions let you filter which incidents trigger a notification on the rule's channel. Validio supports the following condition types:

| Condition Type | Description | Configuration Options |
| :- | :- | :- |
| Owner | Send notifications based on who owns a source. Owners can be assigned on the Sources and Source Details pages. | Select from a list of Owners. |
| Priority | Send notifications based on incident priority. Priority is inherited from the source or validator. Only validator incidents have priority. For more information, see [About Validator Incidents](https://docs.validio.io/v10.1/docs/incidents-and-errors/incidents.md). | Low Medium High Critical |
| Segment | Send notifications only on incidents in selected segments. Each row in a segment chip pairs a **Segment field** name with a **Regex pattern** that is matched against the segment value. A rule can hold one or more segment conditions. Click **+ Add segment condition** on the rule card to add another segment chip. The segment chips combine using DNF logic — see [Tag and Segment Conditions (AND within, OR across)](#tag-and-segment-conditions-and-within-or-across) for details. | Segment field Regex pattern |
| Severity | Send notifications based on their severity. Only validator incidents have severity levels. For more information, see [About Validator Incidents](https://docs.validio.io/v10.1/docs/incidents-and-errors/incidents.md). | Low Medium High |
| Source | Send notifications only when incidents are generated by selected sources. | All sources Select from a list of specific Sources |
| Tag | Send notifications when incidents occur on sources or validators containing the selected pre-defined tags. You can only route notifications based on Label tags. A rule can hold one or more tag conditions. Click **+ Add tag condition** on the rule card to add another tag chip. The tag chips combine using DNF logic — see [Tag and Segment Conditions (AND within, OR across)](#tag-and-segment-conditions-and-within-or-across) for details. For example, to notify on incidents from a specific validator on a source, tag that validator and add a tag condition to the rule for that tag. | Label Custom |
| Type | Send notifications when the selected type of issue occurs. | Schema change Validator incident Source errors Source segment limit exceeded |

## Combining condition types

The logic applied to a notification rule depends on the condition type and on whether values are combined within a single chip or across multiple chips.

### Across different condition types (AND logic)

When a rule sets values on more than one condition type — for example, both a **Source** chip and a **Severity** chip — **AND logic** is applied across them. All chips must match the incident before the notification triggers.

### Multiple values within source, type, severity, priority, or owner (OR logic)

The **Source**, **Type**, **Severity**, **Priority**, and **Owner** chips each accept multiple selections. Within one of these chips, **OR logic** is applied: the chip matches if the incident matches **any** of the selected values. For example, selecting both `High` and `Critical` on the **Priority** chip notifies on incidents at either priority.

### Tag and segment conditions (AND within, OR across)

Tag and segment conditions follow a two-level logic so you can express complex routing rules:

* **Within a single tag or segment chip — AND logic.** All tags selected in one tag chip must be present on the source or validator that generated the incident. Similarly, every `Segment field`/`Regex pattern` row in one segment chip must match the incident's segment.
* **Across multiple tag or segment chips — OR logic.** A rule with several tag chips matches the incident if **any one** of those chips matches. The same applies to segment chips.

For example, a rule with a single tag chip containing `env:prod` and `team:data` only fires when the source or validator has **both** tags. Click **+ Add tag condition** to add a second tag chip with, say, `region:us-east`; the rule then matches an incident tagged either (`env:prod` **and** `team:data`) **or** `region:us-east`. Segment chips work the same way: a chip with rows `country` = `^US$` and `tier` = `^gold$` matches only incidents on the US gold segment, and adding a second segment chip introduces an alternative match using OR.

## Edit or delete a rule

To change the conditions on an existing rule:

1. Open the channel at **Notifications > Channels > *channel name***.
2. In the **Notification rules** section, locate the rule and click a condition chip to change its value. To add another tag chip, click **+ Add tag condition**. To remove an added tag chip, click its **X**.
3. Click **Save** to apply your changes, or **Cancel** to discard them and revert the chips to their previously saved state.

To rename a rule, click **Rename** from the rule's ⋮ menu, enter a new name, and confirm.

To delete a rule, click **Delete** from the rule's ⋮ menu and confirm the deletion. Deleting a rule stops any alerts from being sent for the conditions it defined, but other rules on the same channel continue to trigger.