Skip to main content
Notifications are available automatically to customers who are signed in inside the portal or connected through signed identity. Anonymous customers do not see the notification bell or unread badge.

​
What customers receive

The notification bell can include team replies, request status changes, new comments on followed requests, and newly published changelog entries. Customers can open the related content, mark individual notifications read, mark all read, or delete notifications. Customers manage in-app and email preferences from their portal notification settings.

​
Launcher badge

Launcher mode shows the unread count on the closed launcher button. Counts above nine display as 9+. The badge refreshes after the panel closes and while a server-identified customer remains signed in. Customers who sign in directly inside the widget can also receive the badge through the embedded portal session. Inline mode has no launcher button, so it does not display a launcher badge; the notification bell remains available inside the embedded portal.

​
Confirm notifications work

  1. Open the launcher as a signed-in test customer.
  2. Create a team reply or another supported notification event for that customer.
  3. Close the widget and confirm the launcher shows an unread count.
  4. Open the notification, mark it read, close the panel, and confirm the badge updates.
If no badge appears, confirm launcher mode, customer accounts, and signed identity, then use widget troubleshooting.