--- title: "How to Set up Alerts" description: "Set up alerts to get notified when a model or policy metric crosses a threshold." ---
TL;DR
On a Monitoring Dashboard's Alert Settings tab, click Create New Alert, write a condition over the dashboard's columns (for example, ks_metric < 0.3), pick severity and recipients, and activate. Fired alerts collect on the Triggered Alerts tab and can also be sent via email or in-app notification.
## What is it? Alerts are rules that watch the data in a Monitoring Dashboard and fire when conditions you define are met (a metric breaches a threshold, a review date is approaching, an approval has been stuck for too long). A fired alert can notify users, raise an in-app flag, or send an email. Alerts live on the dashboard's **Alert Settings** tab, and fired alerts collect on the **Triggered Alerts** tab. You'll need write access to the Monitoring Dashboard module, and the dashboard itself must already be set up with a data schema and refresh logic. See [Monitor your Model or Policy](/user-guide/how-tos/monitor-model-policy/). ## How to Create an Alert Follow these steps to create an alert.
#### Open the Create Form Open a Monitoring Dashboard (for a Model, go to **Model Studio → Monitoring Dashboard**; for a Policy, go to **Prospecting**, **Underwriting**, or **Customer Management → Monitoring Dashboard**), then open its **Alert Settings** tab, where existing alerts are listed. Click **Create New Alert** in the top right to open the alert form in a side panel.
#### Fill Alert Details Give the alert a **Name** (for example, `KS below 0.3` or `Review due in 30 days`) and a **Description**. Pick a **Severity**: **High**, **Medium**, or **Low**. This determines the color the alert shows and the tag in front of the email subject line, so recipients can tell at a glance how serious a triggered alert is. Leave **Activate** checked to evaluate on every refresh, or uncheck it to save the alert muted until you're ready.
#### Define the Alert Conditions Under **Alert Conditions**, use the rule builder to write the expression that triggers the alert. Conditions reference columns from the dashboard's Data Schema. Examples: * `ks_metric < 0.3` * `days_to_review < 30` * `approval_status = 'Pending Approval' AND days_in_status > 14` You can combine clauses with **AND** and **OR**, and group them with parentheses. The alert fires for every row that matches.
#### Add Actions Under **Actions**, click **Add Action** to add one or more actions that run when the alert fires. An alert must have at least one action, and you can stack several on a single rule (for example, notify in-app, flag the object, and email the owner). Pick an action type:
Send Notification Send an in-app notification to selected **Recipients** (users or roles picked from the multi-select).
Add Alert Flag Attach a configured **Flag** to the object the alert is watching. When the alert fires, the flag is added to that Model, Policy, or other object and shows up on its details page, so anyone opening it sees it.
Send Email Compose the email sent each time the alert fires. **To:** type a recipient's email, or select an email column from the dashboard so the message reaches whoever the triggering row points to (for example, the model's owner). Click **Cc Bcc** on the right to reveal those fields and add more recipients the same way. **Subject:** a single line, for example `{Alert Severity Icon} {Alert Severity} {Alert Name} has been triggered for Model {ID}`. **Placeholder chips** sit below the subject line: Trigger Date, Alert Name, Alert Severity, Alert Severity Icon, ID, and more… for additional fields. Click a chip to insert it as `{placeholder}`; each email fills it in from the row that triggered the alert. The example above arrives as something like "🔴 High KS below 0.3 has been triggered for Model 4821". **Body:** a rich-text editor. Placeholders work here too, for example: > Hi, > > Alert Notification of {Alert Name} has been triggered for the Model with the following details: > > - Alert Name: {Alert Name} > - Severity: {Alert Severity} > > Please review and take necessary action.
Use the trash icon to remove an action you no longer want. When the alert is complete, click **Save** at the bottom of the drawer. It appears in the Alert Settings list.
## Testing without Waiting for the Next Refresh You don't have to wait for the next scheduled refresh to test an alert. From the **Alert Settings** tab toolbar, click **Evaluate Now** to run all active alerts against the current dashboard data immediately. The button shows the timestamp of the last evaluation in its tooltip. ## Managing Alerts From the row's action icons: * **Mute / Activate** (bell icon): toggle the alert between Active and Muted. Muted alerts stay in the list but do not evaluate. * **Delete** (trash icon, visible only when muted): permanently remove the alert. Mute first, then delete, to guard against accidental removal of an active rule. Click anywhere on an alert row to open its side panel for editing. It also has a **Change History** tab. ## Triggered Alerts Open the **Triggered Alerts** tab to see every alert that has fired. Each row shows which alert fired, which dashboard row it matched, when it fired, and its current status (Open or Closed). Toolbar actions: * **Close Selected Alerts**: mark the selected triggered alerts as Closed (acknowledged). Closed alerts stay in the list for audit but are filtered out of the open count. * **Delete Selected Alerts**: permanently remove the selected triggered alerts. * **Refresh** and **Export to Excel** are also available from the toolbar. The **Column Chooser** icon lets you show or hide columns, and the toolbar **Reset** icon restores the default view state if you've reordered or filtered the grid. ## What's next * [Monitor your Model or Policy](/user-guide/how-tos/monitor-model-policy/) explains how the underlying dashboard data is produced and refreshed, which is what alerts read.