Quick start
- Open your account menu, then Notifications.
- Choose Mark all as read to clear the unread status of currently loaded notifications.
- Use Settings → Alerts for preferences, and Monitoring for recurring scans.
Read and clear recent notifications
Opening Notifications does not mark items read. Select an item to mark that notification read and open its result, or choose Mark all as read to clear unread status for the recent items currently loaded. Items remain in the list; this does not delete scans or activity.
Read status is local to this browser and separated by account and workspace. It synchronizes between tabs using browser storage, but not between devices. If storage is blocked, the current tab can still mark items read and displays a warning. Clearing site data resets read status. Up to 1,000 recent read IDs are retained.
The panel shows up to 20 recent events, not an unlimited inbox. Newly arriving items stay unread even after marking the current list. Refresh reloads the feed; it also refreshes periodically while you are signed in. View activity opens the audit log, not an archive of all notifications.
Scheduled scans
Open Monitoring to manage recurring scans where your plan and role permit them. Current presets are daily, Monday weekly, or first-of-month scans at 09:00 UTC. The deployment scheduler must be configured; a schedule entry alone does not prove delivery or execution succeeded.
Monitor this page on a scan result opens a new schedule form with that URL and a suggested name. Review the frequency and submit the form to create the schedule; following the link alone does not schedule a scan.
Scheduled scans are not included in the base Free configuration. Verify current plan access, recent execution, and errors instead of assuming a scan ran because its scheduled time passed.
Email, integrations, and alert delivery
Settings → Alerts stores notification preferences. Email requires configured delivery infrastructure; Slack and webhooks require valid configured destinations. Saving a preference does not verify that an external message arrived.
Thresholds are operational signals, not certification thresholds. If an alert does not arrive, check the scan result, selected workspace, preferences, integration configuration, and delivery records. A failed feed request is shown as an error with a retry action, not an empty inbox.