Skip to main content

Triage your in-app notifications from the bell to the list

Written by Aurora

Overview

The Notifications experience collects system-generated messages about actions, verifications, inspections, HiPo events, and more. This flow shows how to move from the bell quick view to the full Notifications page, apply filters, update read state, and follow links to related records.

Who can use this

Audience

Typical goal

All users

Stay current on assignments and alerts.

Managers

Scan categories for team risk signals.

Administrators

Confirm critical escalations were acknowledged.

You need access on Notifications. Counts and lists are user-specific.

Before you begin

  • Locate the bell icon in the header; note the unread badge when work is waiting.

  • Decide whether you will also adjust Notification Settings for push or email (see the companion email flow article).

Walk through the flow

Open the full list

  1. Click the bell icon to open the dropdown quick view.

  2. Choose View All to open the Notifications page with the chronological list and filter panel.

  3. Read the header tabs if your build exposes Inbox versus Settings; stay on the inbox tab for triage.

Filter and search

  1. Type at least the minimum characters your UI expects in the search field to narrow titles and messages.

  2. Set category to All or a specific channel such as ACTIONS or VERIFICATIONS.

  3. Optionally set Date From and Date To to bound the list; clear badges or controls when you need a fresh slate.

Mark read state and clean up

  1. For a single row, choose Mark as Read or Mark as Unread so the badge stays honest.

  2. For several rows, select their checkboxes, then use Mark as Read, Mark as Unread, or Delete selected from the bulk bar.

  3. When supported, use Mark all as read for the current page if you have finished reviewing everything visible.

Open related work

  1. Click a notification row to select it.

  2. Use the in-card link or button that opens the related item (for example an action or verification).

  3. After you finish the underlying task, return to the list and mark the notification read.

What happens next

  • Read and unread counts refresh with the API after each action.

  • Deleted notifications disappear from the list and no longer appear in the bell history.

Notes

IMPORTANT: Filters may persist for your session; clear them if a list looks unexpectedly empty.

If the bell never appears, your role may lack Notifications access. If counts look wrong, refresh once after bulk updates.

Did this answer your question?