User Guide

About Notifications

Notifications are the way AlloyScan tells you about events that matter, such as a new device being discovered, an app registration about to expire, a computer stopping its reports, or a user account being created. The feature has three parts: a catalog of subscribable notification templates, automatic system notifications, and delivery channels.

How notifications work

Subscribable template categories

The Notification templates catalog has three categories you can subscribe to:

  • Administrative - app-registration lifecycle events such as App registration expires in 30 days, App registration expires in 7 days, and App registration has expired.
  • Standard - discovery events such as New SNMP device detected, New computer detected, New SNMP device added to inventory, and New computer added to inventory.
  • Conditional - state-based alerts such as SNMP device is not active, Computer is not active, and Software installed on computer.

System notifications

System notifications such as New user email confirmation, Welcome to application, and Password reset are sent automatically when the event occurs. They do not use subscriptions.

Delivery channels

Each subscription specifies one or more delivery channels:

  • Email - sent by the instance Email client (configured under Admin Center > App management > Email).
  • Web browser - surfaced inside AlloyScan via the bell icon in the page header, which opens a Notifications side panel.

Subscription model

Subscriptions bind a recipient to a specific notification template and pick the delivery channel(s). There are two entry points:

  • Bell icon. A user opens the Notifications side panel from the bell button, then uses the gear icon labeled Manage alert subscriptions to manage their own subscriptions.
  • Admin Center > Site Settings > Notifications > Subscriptions. Administrators see all users' subscriptions, grouped by user, with Notification and Delivery channels columns.

Templates themselves can be customized per site or imported in bulk via Import JSON on the Notification templates page.

Specialized event behaviors

  • App registration expiration. Administrative templates fire at 30 days, 7 days, and expired milestones. An expired registration also surfaces as a persistent red banner on every page.

Why this matters

  • Operational awareness. Standard and Conditional templates keep you ahead of changes in your inventory, such as new endpoints, devices going stale, or software appearing where it should not.
  • Compliance and integration health. Administrative templates protect you from silent failures of API integrations: by the time an app registration expires, you have already received two warnings and a final expiration notice plus a red banner.
  • Account hygiene. System notifications carry user lifecycle messages such as confirmation, welcome, and password reset that depend on a working email transport.

Key distinctions

  • Notifications are message-style alerts sent to subscribed recipients or triggered automatically by a system event. The Notifications log records delivery status and is a separate site-scope log.
  • The Web browser delivery channel posts in-app messages reachable through the bell icon. It is distinct from operating-system desktop notifications.
  • Templates define what is sent and which event triggers it; Subscriptions define who receives it and on which channel.

Limitations

  • Email delivery requires the instance-wide Email client to be configured. Without it, no Email-channel notification will be delivered.
  • Some event types may not be available on every site.

Note: Details may vary by deployment.