Skip to Content
Unified docs shell with shared Classifyre tokens and acid-green highlight accents.
Notifications

Notifications

Classifyre is quiet by default. If you’re not hearing from it, everything is running normally. Notifications only appear when something genuinely needs your attention — a scan failing, unusual activity, or a milestone worth knowing about.

The Bell

The notification bell lives in the top-right corner of the app. A red badge shows how many unread notifications you have. Click it to see your latest alerts.

Live preview

Click the bell above to open it

Badge number

How many unread notifications you have. Disappears when everything is read.

Coloured background

Unread items are highlighted based on severity — red for high, yellow for medium, and so on.

Mark all read

Clears the badge and marks every item as read in one click.

What Triggers a Notification

Only five events send a notification. Everything else is intentionally silent — a successful scan with no anomalies produces no noise.

SCAN
Scan Failed

A scan could not finish. The notification title includes how many times in a row this source has failed.

Click "View scan" to see the specific error. Common causes: expired credentials, network connectivity issues, or the source being temporarily unavailable.
SCAN
Scan Recovered

A previously failing source completed its scan successfully.

No action needed — this is good news. You can optionally review the scan results to confirm everything looks normal.
FINDING
Findings Spike

This scan found significantly more findings than usual — more than 3× the recent average, with at least 20 more than baseline.

Review the scan immediately. This may indicate newly exposed content, a newly connected service, or a change in scanning scope. If unexpected, investigate the source.
FINDING
Large Drop in Findings

The number of findings dropped sharply compared to the previous scan — a 3× or greater decrease of at least 20 findings.

Verify this was intentional. A large drop can mean a successful cleanup, but it can also signal that the scanner lost access to content or that a configuration changed unexpectedly.
SOURCE
First Scan Complete

A newly added source finished its very first scan.

Review the initial findings — this is your baseline for that source. Any findings here were already present before Classifyre started monitoring.

Severity Levels

Each notification has a severity that reflects how urgently it needs your attention.

LevelColourWhat it signalsEvents
HighOrange–redNeeds attention soonScan Failed, Findings Spike
MediumYellowWorth investigatingLarge Drop in Findings
InfoGreyGood news or FYIScan Recovered, First Scan Complete

High-severity notifications are also marked as Important automatically, so they stay visible even after you read them. You can toggle the Important flag on any notification manually.

The Notifications Page

The bell shows your most recent alerts. For the full history — with filtering by severity, type, and read status — open the Notifications page from the sidebar.

From there you can:

  • Filter by severity, type, or source
  • Mark a subset as read using the active filters
  • Dismiss notifications you no longer need
  • Pin notifications as Important to keep them accessible

Notifications are stored indefinitely and are not automatically deleted, so you can always look back at when a source first failed or when an anomaly was detected.

Last updated on