Skip to content

Notification management

The admin-level notification management offers an overview of all workspace notifications - not just your own. You see scan results with URL count and findings, error messages for failed scans, and warnings about low token balance and limits from guardrails. This way you keep operational incidents and resource risks centrally in view.

Admin overview of all notifications

Overview of all workspace notifications for admins

  • Workspace-wide - admins see notifications for the entire team, not just their own.
  • Prioritisation - important messages can be distinguished more quickly from purely informational ones.
  • Transparency - supports team coordination when several people look after projects.

Scan results with URLs and findings

  • URL count - shows the scope of the checked pages in the context of the message.
  • Findings - hints about detected problems or anomalies from the run.
  • Follow-up - from here you can typically jump to the project or the detail view.

Errors for failed scans

  • Error cause - short info or code helps with the first classification.
  • Operational - quick response reduces downtime for recurring configuration issues.
  • Escalation - admins can check affected projects or profiles and inform owners.

Token warnings and guardrail limits

  • Low balance - hints before scans stop due to missing tokens.
  • Guardrails - messages when configured limits are reached or nearly reached.
  • Planning - use the warnings for top-up or adjusting scan intensity.

Read status and team coordination

  • Overview - you can see which messages still need attention.
  • Coordination - within the team you can avoid the same incident being worked on by several people in parallel.
  • History - older entries remain traceable as long as the product keeps a history.

Filters and focus (if available)

  • Type - narrow down to scan results, errors or warnings.
  • Time range - helps in analysing recurring errors within a release cycle.
  • Relief - reduces noise when the list grows very long.

Notes

  • Set up internal responsibilities for responding to error and token messages.
  • Not every notification requires immediate action - bundle recurring topics into team routines.
  • Combine this overview with billing and project settings for consistent operations.

Published on qualivise.ai