The bell in the top bar is the in-app channel. It shows your notifications and, if you may view alarms, the latest open alarms of your organisation, in one list. It is always on: there is no switch for it, because it is the feed inside the product.
What the bell shows
| Item | Comes from | Read when |
|---|---|---|
| Notifications | Alarm notifications, rule and flow notifications, notices from the platform (for example “place is back on Auto”, “Rule name needs attention”, device notices) | You click it, or Mark all read. |
| Alarms | The latest 5 open and acknowledged alarms, with severity, title, device and time | An alarm counts as unread while it is Open. |
The list is newest first. Show filters it: All, Alarms or Notifications.
The badge counts unread notifications plus every open alarm (not only the 5 shown). Its label reads “Notifications, n unread”.
Working from the bell
- Click a notification to mark it read and open its page in the app (for an alarm notification, the alarm). Links to other sites are never opened from the bell.
- Mark all read marks every notification read.
- An open alarm has an inline Acknowledge button, if you may acknowledge alarms.
- Acknowledge all acknowledges the open alarms after asking, with an optional note.
- View all alarms opens the Alarms page. See Working with alarms.
The bell updates live. Alarms follow the organisation’s alarm events as they happen.
How long the feed is kept
| Rule | Value |
|---|---|
| Items kept per person | The newest 50. Older ones are dropped as new ones arrive. |
| How long | 7 days after the last new item, then the feed is cleared. |
An administrator can change the days in Settings > In-app Notification Settings > Keep the notification feed (days): 1 to 365. The newest 50 items are kept either way. Changing it needs Change in-app notification settings (Admin by default).
Alarms in the bell are not part of the feed: they come from the alarm list and stay until they are resolved.
Who gets in-app notifications
Members of your organisation, named directly, through a role or through a team. E-mail addresses and phone numbers have no feed. In-app notifications are not held back by quiet hours or by the person’s channel switches.
What an in-app notification contains
Its title and text in plain form. HTML from a flow is shown as text; attachments are not shown.
Alarm notifications versus alarms in the bell
You may see both for the same alarm:
- the alarm item is there because the alarm is open and you may view alarms, whether or not you were told about it;
- the notification is there because an alarm rule or flow named you (directly or by role) as a recipient.
To stop the notification but keep seeing alarms, ask your administrator to change the rule’s recipients or minimum severity. See Alarm notifications in depth.