Choose your email notifications

Use Settings → Notifications → Your email notifications to choose the follow-up emails you receive for the current organization. Every member, including viewers, controls their own subscription. Changing your settings does not change another member’s emails or your organization’s scan schedule.

Default emails by plan

Starter sends only a weekly digest after the scheduled scan. Known exploited vulnerabilities appear first, and final scan failures are included. Starter has no additional alerts or advanced email options.

Pro and Team start with a daily digest at 08:00 UTC. All additional email alerts start off. You can select a weekly digest, disable the digest, or turn off all follow-up emails. An empty digest is skipped. Unsent digests from a configuration outage are folded into the next scheduled digest instead of arriving as a burst.

Choose your digest

On Pro and Team:

1. Open Settings → Notifications in the organization you want to configure.
2. Choose Email digest: daily, weekly, or off.
3. Set the Digest sending time, timezone and, for a weekly digest, weekday. The time follows local daylight saving changes. A repeated clock hour does not create a second digest; a missing clock hour sends after the clock advances.
4. Select the Digest sections: new findings and KEV, available updates, final scan failures, and SLA breaches.
5. Set Digest severity for findings and updates, then select Save email preferences.

New findings, KEV changes, final failures and SLA crossings are reported since your previous delivered digest. Available updates summarize the current open queue. Starter keeps relevant KEV findings first in its weekly digest.

Add email alerts

On Pro and Team, each Additional email alerts switch is independent:

• Known exploited vulnerabilities: a vulnerability affecting your organization enters the KEV (Known Exploited Vulnerabilities) catalog. An existing finding can qualify when it later enters KEV.
• New findings: a newly observed finding meets your New finding severity.
• Final scan failures: a repository’s scan still fails after its retries finish. Intermediate retry failures do not send separate emails.
• SLA breaches: a critical finding crosses the organization’s remediation deadline.

Enabling multiple categories can produce multiple emails per day. Events from one completed scan batch are grouped. An unchanged finding is not sent again on every scan, and enabling an alert does not send a backlog of existing events.

Stop follow-up emails

Turn off Follow-up emails and save, or select Unsubscribe from follow-up emails in a received email and confirm. Your email application’s unsubscribe action can also stop follow-up emails. Merely opening the unsubscribe page does not change your subscription.

This stops your digests and selected email alerts in that organization. Invitations, billing messages and explicitly requested test emails remain available. You can enable follow-up emails again in Settings.

Plan changes and shared delivery

If your organization moves from Pro or Team to Starter, your advanced choices stay saved. Only the Starter weekly digest applies while downgraded. Returning to Pro or Team restores those choices without sending the accumulated alert backlog. Unsubscribing still stops follow-up emails on every plan.

Organization admins separately manage scheduled scans, Slack and webhook destinations. These personal preferences affect email only.

Digests → Preview email saves a preview without emailing organization members. Delivered email digests appear in digest history. Shared previews do not expose another member’s personal unsubscribe link.

Review digest history

Each entry in Digests shows the recorded recipients, channel, delivery status and a View digest action. Slack entries identify the configured destination; the webhook URL is never displayed. If no recipient was recorded, the entry says Recipients unavailable.

Open Delivery details for item counts, top risk and the recorded delivery time. List dates are relative; hover over a date for its exact UTC timestamp. The exact date is also available to screen readers. Realtime alert history is folded below the digest list.