There's no dedicated notifications feed behind the bell icon in your dashboard header — it's assembled fresh on every page load from four different tables that already record real events elsewhere in the product.
Each source shows up to 5 recent entries:
All four are combined into one list, sorted so the newest event from any source appears first — they're not grouped by type.
A new device connecting is the one event two of these sources could otherwise both describe — the alert firing and the device itself showing up. Only one notification appears for it, and clicking it takes you straight to that device's page — unlike other alert notifications (offline, device rejected, and so on), which open your notifications page instead.
If you can't view alerts, devices, groups, or team invitations from their own dedicated pages, you won't see them here either. Team invitations only ever show for the account owner, matching how the Team page itself hides that section from every other role.
For a team member scoped to specific groups rather than the whole fleet, devices and groups in the notification list are limited to what's actually in scope. Alerts work differently: since alerts aren't scoped to individual groups at all, a group-scoped team member sees no alert notifications here, not a filtered subset.
Closing a notification only affects your own view. If another team member has access to the same dashboard, dismissing something doesn't dismiss it for them — each person's dismissals are tracked separately, tied to who's actually logged in, not to the account being viewed.
The dropdown only ever shows your 6 most recent notifications, but the badge number reflects your real total of undismissed notifications, up to 9 — beyond that it shows "9+". If you have more than 6 undismissed notifications, the badge number will be higher than what you can actually see listed at once.
If you have nothing new, the dropdown simply says "No recent activity yet."