Skip to main content
Prizm can deliver data quality alerts, anomaly notifications, SLA breach warnings, and scheduled digest reports directly to email recipients or distribution lists. Email notifications require no additional software — any valid SMTP server or cloud email provider is supported.
Email notification configuration — SMTP settings, recipient groups, and alert routing

​
Prerequisites

  • Access to an SMTP server, or credentials for a cloud email provider (Gmail, SendGrid, AWS SES, etc.).
  • Valid email addresses or distribution list addresses for recipients.
  • Network connectivity from Prizm to the SMTP host on the configured port.

​
Configuration

​
SMTP Settings

FieldDescription
SMTP HostHostname or IP of the outbound mail server (e.g., smtp.gmail.com, email-smtp.us-east-1.amazonaws.com).
PortSMTP port — typically 587 (TLS/STARTTLS) or 465 (SSL).
EncryptionChoose STARTTLS, SSL/TLS, or None.
UsernameSMTP authentication username.
PasswordSMTP authentication password or app-specific password.
From AddressThe sender address that appears in recipients’ inboxes (e.g., prizm-alerts@yourcompany.com).
From NameDisplay name shown to recipients (e.g., Prizm Data Quality).

​
Recipient Groups

Configure named recipient groups to route different alert types to different teams:
GroupSuggested Recipients
Data EngineeringReceives anomaly detections and schema change alerts.
Data GovernanceReceives SLA breaches and rule violations.
Executive DigestReceives scheduled daily/weekly quality summary reports.
Use distribution lists or email aliases rather than individual addresses. This makes it easy to update recipients without reconfiguring Prizm.

​
Notification Types

Notification TypeDefault TriggerEmail Content
Anomaly AlertAnomaly detected above severity thresholdAffected asset, metric, deviation magnitude, and a link to the Prizm anomaly detail page.
SLA BreachQuality SLA threshold crossedSLA name, metric, breach value, and breach duration.
Schema ChangeColumn added, removed, or type changedTable name, change type, and before/after schema comparison.
Rule ViolationCustom rule threshold breachedRule name, asset, actual vs. expected value.
Daily DigestScheduled (default: 8 AM local time)Summary of all open issues, resolved issues, and top anomalies from the past 24 hours.
Weekly ReportScheduled (default: Monday 8 AM)Weekly quality trends, top affected assets, and SLA compliance summary.

​
Alert Routing

Route alert types to specific recipient groups in Settings → Integrations → Email → Routing Rules: 
Anomaly (Critical, High)  → data-engineering@yourcompany.com
SLA Breach               → data-governance@yourcompany.com
Weekly Report            → exec-digest@yourcompany.com
If no routing rule matches an alert, Prizm sends it to the default recipient group configured under Settings → Integrations → Email → Default Recipients.

​
What’s next

Slack Integration

Send Prizm alerts to Slack channels for real-time team visibility.

Teams Integration

Route Prizm notifications to Microsoft Teams channels.

Alert Rules

Configure which events and thresholds trigger email notifications.

Anomaly Detection

Learn what triggers the quality events that generate email alerts.