Notifications

Notifications keep you informed about what is happening in your workspace without polling. The bell icon in the console top bar opens the notification center, shows an unread count badge, and delivers events in real time as discovery, scanning, and analysis pipelines produce results. Every notification is tied to a concrete event in the workspace — a new asset discovered, a vulnerability analysis completed, a new finding reported, or an invitation to join a workspace. Instead of waiting to check the dashboard, you get the signal the moment it exists.

​

Key concepts

​

Notification center

The bell icon in the console top bar opens the notification center. An unread count badge on the bell shows how many notifications you have not read yet; the badge updates automatically as new events arrive. The center is the primary surface for consuming notifications:

• Bell icon + badge — the entry point; the badge is the live unread count.
• Notification list — recent events in chronological order, newest first.
• Click-through — opening a notification takes you to the related item (for example, the affected asset or finding).

​

Real-time delivery

Notifications arrive in real time. When the console detects a new event, the unread count and the notification list update without a page refresh — you see the event the moment it happens.

​

Integrations

Beyond the in-console center, notifications can be forwarded to external channels. The platform supports integration with Slack, Telegram, and Webhook endpoints, so critical events can also reach your team chat or automation. See Integrations to configure forwarding.

How do integrations relate to the notification center?

The notification center and external integrations observe the same events. The center is the built-in, workspace-scoped view; integrations forward those events to Slack, Telegram, or a Webhook endpoint so people and systems outside the console can act on them. You can use both at once — nothing about the in-console center changes when forwarding is configured.

​

Notification types

Notifications are classified by type. Each type corresponds to a distinct event and a typical follow-up action.

What is the difference between a new vulnerability found and an analysis completed?

A new vulnerability found fires when a scanner detects a new finding on an asset — the raw signal that risk exists. An analysis completed fires when the analysis stage finishes processing results — the signal that findings have been enriched and are ready for review. In practice, the first tells you something new appeared; the second tells you it is ready to act on.

​

Event-driven workflows

Each notification type maps to a concrete follow-up workflow. Use this mapping to decide what to do when a notification arrives: The two vulnerability types form a natural pair: a new vulnerability found alerts you that risk exists, and an analysis completed tells you the analysis is ready for review. Between the two, no new finding can slip past your workflow unnoticed.

​

View and manage notifications

​

How notifications arrive

The console maintains a real-time connection to the notification stream. When a new event happens:

1. The event is delivered over the stream channel.
2. The notification center list updates in place — no page reload.
3. The unread count badge increments.

Notifications arrive in real time, designed for near-instant delivery of new workspace events.

​

Real-time delivery vs. polling

Notifications are push-based: events arrive as they happen, and the console does not need to re-request the list to notice them. The unread count is also available separately for anything that just wants the number without reading the full list — for example, an external status indicator. In the console itself, the badge and list stay in sync automatically.

​

Workspaces and integrations

How do I keep track of notifications across multiple workspaces?

Notifications are per-workspace, so the bell badge only reflects the workspace you are currently using. To review another tenant’s activity, switch workspaces and open the center again — the badge, the list, and the unread count all follow the switch. If you need a single place for events from many workspaces, configure Integrations (Slack, Telegram, or Webhook) to forward them to one external channel.

​

Best practices

• Keep the unread badge from accumulating: review notifications daily so events like a new vulnerability found do not sit unnoticed.
• Treat a new vulnerability found as the trigger to open the Vulnerabilities page and triage — the notification is your earliest warning signal.
• Use a new asset detected to spot scope creep early: unexpected new assets deserve review before they are enabled for scanning.
• Route critical event types to external channels via Integrations (Slack, Telegram, or Webhook) so the right people see them even when they are not in the console.
• Remember notifications are workspace-scoped — switch workspaces to review the activity of a different tenant.
• Set up a review cadence around the vulnerability pair: a new vulnerability found triggers triage, an analysis completed triggers remediation updates — both should be handled before the next scan cycle.
• Use Integrations to forward high-signal types (for example, a new vulnerability found) to the channel your team actually watches.

​

Related