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

# Notifications

> Send dbt-run and integration (source-load) failures to Slack or email.

Platinur delivers operational events to Slack or email. Notifications are configured on the **Settings** page in the **Notification Preference** card: pick a channel, fill its fields, **Save Changes**, then **Send Test**. Channels are set up one at a time. A single **What to send** list below the channels controls which events fire, and applies to every configured channel at once.

Without a configured destination, failures appear only in Monitoring.

## What to send

The **What to send** toggles pick which failures any configured channel receives — one shared set across every channel, both on by default. Turning both off silences notifications without removing your saved destinations.

## Events

* **dbt failures** (`dbt_failed`) — a scheduled dbt run, or the Evidence (dashboards) rebuild that follows it, fails.
* **Integration failures** (`integration_failed`) — a source load into your warehouse fails. The failure also shows in the integration's **Runs** view in Integrations with the full log.
* **Test** (`test`) — sent by the Send Test button.

Everything else — proposal validation, assistant-task, connection-test, and schema-drift failures, plus informational events like ready proposals or production deploys — still surfaces in **Monitoring**; it just isn't sent as a notification.

## Slack

One field: **Slack Webhook URL** — a Slack incoming-webhook URL (`https://hooks.slack.com/services/...`). Each event posts a message with the event title and detail, prefixed `[Platinur]`.

## Email

One field: **Email address(es) to notify** — enter one recipient, or several separated by commas. Platinur sends the message from its own managed email service, so there is no SMTP host, port, or credential to configure. The channel counts as configured as soon as at least one address is saved; the subject is `[Platinur] <event title>` and the body carries the event detail plus metadata.

If email delivery has not been enabled on your deployment yet, the card notes that email alerts are logged rather than sent — use Slack until it is available.

## Send a test

The **Send Test** button below the form delivers a test event to every configured channel and reports the result; it is disabled until a destination is saved. Every test is recorded in the audit log. The API equivalent is `POST /api/notifications/test`, which accepts an optional `kind` (`slack` or `email`) to test a single channel.

## Delivery and secrets

Delivery is best-effort: each channel times out after 10 seconds, and a delivery failure never blocks or fails the underlying run — failed runs always remain visible in Monitoring.

Payloads carry only event context — titles, run summaries, schema and connector names, task and proposal ids — never credentials. The Slack webhook URL is stored encrypted as a secret reference and is not displayed again after saving; paste a new value to replace it. Email recipient addresses are stored in plain config (they are not secrets).