Notifications
Owners and admins configure delivery in Settings → Notifications. Other roles can read the settings. Notifications are separate from sign-in and team-invitation email.
Configure alerts
- Under Alerts, enable High and critical detections, Unknown AI tools, or both.
- For unknown tools, set Minimum reporting devices to a positive whole number. The default is 5 devices. These are reporting devices, not a count of employees.
- Under Destinations, add comma-separated Email recipients (up to 20), a Slack webhook URL, a Webhook URL using HTTPS, or a combination. The Slack field takes your channel's incoming webhook URL.
- Review the Notification plan. While editing, it shows Preview of changes; this preview is not a saved configuration.
- Select Save notifications and wait for confirmation. Discard changes restores the saved settings.
Alerts are checked every 15 minutes, with repeated findings limited to one alert per tool and alert type in 24 hours. Updates apply to future alerts and summaries. An enabled alert needs at least one destination to reach your team.
Invalid email addresses, more than 20 recipients, incomplete HTTPS URLs, and invalid device thresholds are flagged before saving. If saving fails, your edits remain available. Leaving an edited form asks whether to keep editing or discard changes; a pending save finishes before navigation proceeds.
Weekly summary
Enable Email a weekly summary and add email recipients. The summary covers detections, most-used AI tools, and tools awaiting review from the last seven days. It is sent Mondays at 14:00 UTC.
The weekly summary goes to email only. Slack and HTTPS webhooks receive alerts. The Notification plan shows when the summary is enabled but has no recipients.
Check delivery
Saved destinations confirm configuration, not successful delivery. Blank does not offer a test-send button on this screen. Check the receiving inbox or service when an eligible alert or weekly summary is due; account for the alert schedule and repeat limit before diagnosing a missing message.
HTTPS webhooks receive a JSON POST using the blank.alert/v1 schema. Webhook URLs may include credentials: use your service's protected destination and keep the URL out of support messages. For help, share the approximate time and delivery channel through Support.
For a dated report rather than a notification, use Evidence packs. For a filtered investigation you revisit, use Saved views.