Skip to content
Guide contents

User guide2 min

Workspace alerts

Every scan event from every site in the workspace, newest first, one row per scan. It is the same list as the bell in the top bar, with room to read it.

How to get there#

Two ways into the same list.

  1. 1

    Workspace alerts in the rail

    Shown when no site is open. The badge beside it is the unread count.

  2. 2

    Or the bell in the top bar

    Available from anywhere, including inside a site. The bell shows the same rows in a small panel.

app.pixyscan.com/w/…/alerts

Workspace alerts: Unread and All tabs, Mark all read, then a row per scan with the site name, how long ago it ran, the score badge, any score movement and the completion status.
One row per scan, not one per finding, so a workspace of thirty sites stays readable.

Reading a row#

The scan, then what it raised.

FieldExampleWhat it does
TitleNode.js scan 3The scan, with the site name and how long ago it finished beside it.
ScoreScore 84What that scan scored.
Movement84 → 83Shown only when the score changed from the previous scan.
New critical issueNamedA critical check started failing that was passing before. Its name is printed underneath.
StatusCompletedOr Failed, because a scan that could not finish is worth knowing about.
Blue dotUnreadIt clears when you open the row.

Click a row to open that scan. Mark all read clears the badge without opening anything.

Which events appear is a per-site setting

The events raised, and whether they also go out by email, Slack or webhook, are configured on each site. Site settings → Alerts

If the product does not match this page, the page is wrong and we would like to know. Tell us