Notifications Overview

Notifications keep you informed when Odin Scan discovers security findings in your repositories. Instead of manually checking the dashboard after every analysis, you configure delivery channels and alert policies so that findings reach you automatically through Slack or email.

How Notifications Work

The notification flow follows a straightforward pipeline:

1. An analysis completes and produces findings.
2. Odin Scan evaluates your alert policies against the findings.
3. If any policy matches (based on severity thresholds), a notification is dispatched to the configured channel.
4. The notification is recorded in your notification history with delivery status tracking.

Each notification includes a summary of the analysis results – the repository name, branch, finding counts by severity, and a direct link to the full report.

Delivery Channels

Odin Scan supports two delivery channels:

• Slack – sends a formatted message to a Slack channel via an incoming webhook. The message includes finding counts with severity indicators and a button linking to the full report.
• Email – sends a styled HTML email to one or more recipients. The email includes a severity breakdown table and a link to the full report.

You can configure multiple channels and assign different alert policies to each one. For example, you might send critical findings to Slack for immediate attention while routing all findings to an email digest.

In-App Notifications

Beyond external delivery channels, Odin Scan provides real-time in-app notifications:

• Bell icon – a notification bell in the dashboard header displays an unread count badge when new notifications arrive.
• Toast alerts – brief pop-up messages appear in the dashboard when a notification is delivered in real time.

In-app notifications are always active and do not require any channel configuration.

Plan Requirements

Notifications are available on Pro and Ultra plans. Free-tier users can view in-app notifications but cannot configure external delivery channels or alert policies.

Next Steps

• Channels – set up Slack webhooks and email recipients
• Alert Policies – create rules that trigger notifications based on finding severity
• Notification History – monitor delivery status and retry failed notifications