Notifications
Notifications deliver alerts and updates to users within Tagnet. They can be triggered by workflows, system events, or read signature mismatches, and are displayed in the notification bell in the navigation bar and on the full Notifications page.
Note: Notifications does not have its own entry in the navigation menu. It's a personal inbox for every authenticated role, reached through the bell: click the bell to see recent notifications, then View all notifications for the full page. There are no pop-up alerts for individual notifications; new arrivals show up as an updated unread count on the bell instead.
Overview
Each notification has a title, optional body content, a type (Info, Success, Warning, Error), and a priority level. Notifications can be targeted to a specific user, all users within an access scope, or broadcast to everyone.
From the Notifications page you can:
- View all notifications sent to you
- Search and filter by title, content, type, or priority
- Read notification details with rendered content
- Mark notifications as read (individually or in bulk)
- Navigate to related workflows or scan events from notification context links
Permissions
All authenticated users can view their own notifications; no specific permission is required, and this holds for every role including Operator, even though Operator has no access to Scan Events or Workflows (including runs, templates, and the deprecated movement rules). Notifications are filtered by targeting:
| Targeting | Who Sees It |
|---|---|
| User-targeted | Only the specified user |
| Scope-targeted | All users assigned to that access scope |
| Broadcast | All users in the system |
The Notifications Grid
Columns
| Column | Description |
|---|---|
| Icon | Type indicator: checkmark (Success), warning (Warning), error (Error), info (Info), or tree icon (Workflow source) |
| Title & Preview | Notification title (bold if unread) with a preview of the body content |
| Priority | Color-coded chip: Critical (red), High (orange), Normal (default), Low (gray) |
| Date | When the notification was created |
| Checkbox | For selecting multiple notifications |
Unread notifications appear with bold text and a highlighted background.
Search
Filter notifications by title, body text, type, or priority using the search bar.
Bulk Actions
Select multiple notifications using checkboxes, then click Mark Read to mark all selected as read in one action.
New Arrivals
The list does not refresh itself while you're viewing it. When a new notification arrives, the Refresh button in the page header picks up a small New badge (after a brief delay, so a burst of arrivals doesn't flicker the badge on and off). Click Refresh to reload the list and clear the badge. The bell icon's own unread count, in contrast, updates live.
Notification Details
Click any notification to open its own page at /notifications/{id}, which automatically marks it as read, the same way opening an email does. The page shows:
- Header: Type icon, title, and unread badge
- Type and Priority: Displayed as colored chips
- Timestamps: When created and when read
- Body: Full content rendered as formatted HTML (supports Markdown formatting)
- Delivery: Per-channel delivery status (see below), shown when the notification was dispatched to an external channel such as email
- Related Items: Context links to related entities (if available):
- Workflow: Opens the workflow's own detail page
- Scan Event: Opens the scan event's own detail page
- External Link: Opens a URL in the browser
Delivery status
When a notification is fanned out to an external channel (for example, email), the detail page shows a Delivery section listing each dispatch row:
| Status | Meaning |
|---|---|
| Pending | Queued for delivery or waiting for a retry. |
| Sending | Provider call in flight. |
| Sent | Provider accepted the message. |
| Failed | Permanent non-retryable failure. |
| DeadLettered | Retry budget exhausted. An administrator can re-queue from Email Delivery. |
Each row shows the channel, recipient address, and the provider that attempted delivery. Failed and dead-lettered rows also show the last error message. For full retry controls and detailed error context, open Email Delivery, a tab of the System page.
In-app-only notifications (no email dispatch) do not show a Delivery section.
Notification Types
| Type | Icon | Use Case |
|---|---|---|
| Info | Blue info circle | General information and updates |
| Success | Green checkmark | Completed operations or positive confirmations |
| Warning | Amber warning triangle | Conditions that need attention |
| Error | Red error circle | Failures or critical issues |
Priority Levels
| Priority | Color | Intended Use |
|---|---|---|
| Critical | Red | Requires immediate attention |
| High | Orange | Important but not urgent |
| Normal | Default | Standard notifications |
| Low | Gray | Informational, low urgency |
How Notifications Are Created
Notifications are typically generated by:
- Workflows: Workflow actions can create notifications as part of their execution, targeting specific users or scopes
- System events: Scan events that do not match a read signature, device alerts, and other system-level triggers
- Administrative actions: System-generated notifications for important events
Best Practices
- Check notifications regularly: The notification bell in the navigation bar shows your unread count. Click View all notifications in the bell dropdown to reach the full page; there is no separate nav item.
- Refresh to see new arrivals on the list page: The list doesn't auto-reload; watch for the New badge on the Refresh button.
- Use bulk mark-read: Select multiple notifications and mark them as read to keep your inbox manageable.
- Follow context links: When a notification references a workflow or scan event, click the link to see the full context.
- Search by type: If you're looking for errors or warnings specifically, use the search bar to filter by type.