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

# Alerts

> Configure email alerts for failed pipelines at workspace and resource level.

Pipeline runs can fail for many reasons. **Alerts** help you react quickly by sending email notifications when runs fail.

Nekt supports two types of alerts:

* **Global alerts**: workspace-level email recipients that receive notifications for **any** failed pipeline.
* **Per-resource alerts**: user-level alerts that apply to specific sources, queries, notebooks, histories, or destinations.

<Info>Global alerts are available on all **paid plans**.</Info>

## Global alerts (workspace-level)

Owners and admins can configure global alerts in **Settings → Alerts**.

* Add one or more email addresses to receive notifications when **any** pipeline fails.
* These emails don’t need to enable alerts on each pipeline individually.
* Use this to notify central mailboxes (e.g. `data@company.com`) or on-call teams.

Global alerts are applied **in addition to** any per-resource alerts users configure for themselves.

## Per-resource alerts (user-level)

Any user can enable alerts for specific resources they care about:

* Open the details page of a **source, query, notebook, history, or destination**.
* Toggle the **Alerts** switch in the upper-right corner.

These alerts are:

* **Per user**: each user enables alerts for their own pipelines.
* **Per resource**: you choose exactly which pipelines you want to follow.
* Sent to the email address you use to log into Nekt.

You cannot enable per-resource alerts on behalf of other users in your workspace.

## Bulk-manage alerts from lists

On the list pages for **Sources**, **Destinations**, **Queries**, **Notebooks**, and **Histories**, you can enable or disable alerts for multiple pipelines at once:

1. Go to the relevant list (e.g. **Sources**, **Queries**).
2. Select the pipelines you want to update.
3. Use the bulk actions menu to enable or disable alerts for all selected items.

This is useful when you onboard a new project, change alerting strategy, or need to pause alerts for a set of pipelines temporarily.

For more on investigating failures and reading run logs, see [Runs – Logs](/runs/logs).