Skip to content
Retailium Help Center home

Use the Notification Center

Summary: You will use the notification bell to see conflict alerts, case-access requests and responses, and act on them.

The Notification Center is a bell in the application header that gathers five alert streams into one inbox, with a full history behind it. It is visible to every internal role (everyone except Store Associates, who never reach the application shell).

The five streams

StreamWhat it isWho sees it
Conflict AlertsAn entity you created or linked (a member, vehicle, organization, address, or contact) matches one on another case in the same categoryThe owner and investigator of the conflicting case
Cross-Category MatchesAn ORC ↔ Drug Diversion entity matchAdministrators and the three manager roles only
Entity Link RequestsA request to copy an entity onto a case in another categoryAdministrators and the three manager roles only
Case Access Requests (incoming)Someone asks for access to a case of yoursThe assigned case manager; the moderating roles see all
Case Access Responses (outgoing)The outcome of a request you madeThe person who asked

Two streams are wired up but never fire today. Nothing currently generates a Cross-Category Match or files an Entity Link Request: the streams render and can be cleared, but you will not see new items in them. Granting a case-access request adds the requester to the case as a read-only collaborator; it does not change the case's labels or owner.

The Chinese Wall in notifications

Cross-Category match alerts and entity link requests are shown only to Administrators and the three manager roles: never to investigators, analysts, auditors, viewers, partners, or field roles. An investigator must not learn that a cross-category match exists at all. Platform Administrators see the bell and the conflict/access streams but hold none of the moderation rights.

How delivery works

  • All five streams refresh every 30 seconds while the application is open. A new alert appears within half a minute: there is no instant push.
  • Notifications are never emailed and never sent to a phone. The bell is the only delivery mechanism, and nothing is delivered while the application is closed.
  • The bell's count combines unread conflict alerts, unread cross-category alerts, pending link requests, pending incoming access requests, and undismissed outgoing responses. It caps at 9+.
  • The popover shows only the most recent items per stream; older ones are reached from history. "Mark all read" clears conflict alerts only: the other streams are cleared by acting on each item.
  • With nothing pending, the popover says so plainly. A failed load shows an error with a retry, so "no alerts" always means no alerts.

Notification history

The All button in the popover opens a full history of every notification, including ones already acted on. It is reachable only this way (not from the sidebar).

  • Filter to all notifications, conflict alerts, cross-category matches, link requests, or case access; paged 25 at a time.
  • The chosen filter and page are part of the address, so a view can be bookmarked or shared with a colleague who has the same rights, and survives a reload.
  • The history cannot be exported and cannot be filtered by date or by person.