Skip to content
Design System
GitHub

Notifications

The bell in the top bar: what happened while you were away, grouped by day, read or unread.

Overview

When to use

  • Finished missions, ready reports, installed firmware, changes someone else made.
  • Anything worth knowing later that needs no action now.

Use something else

  • An abnormal condition that needs someone to act (a robot stuck, a battery about to run out, an emergency stop): an alarm, with the Alarm component and the island.
  • Settings for which events notify whom: Settings (notification matrix).

Blocks

Notification center

The bell in the top bar with its unread count, opening notifications grouped by day: a popover on wide screens, a bottom sheet on phones. Mark one or all as read, filter unread. For things worth knowing later; alarms that need action stay with Alarm and the island.

Install
npx shadcn add @syncrobotic/notification-center

Usage rules

  • Notifications are not alarms. Anything that needs action is an alarm first; it may also leave a notification, never only one.
  • Unread is a dot and weight, said in words to screen readers, never colour alone.
  • Each notification says what happened, which robot and site, when, and links to the thing itself.
  • Esc closes and puts focus back on the bell; arrow keys move through the list.