Overview of the Notifications pattern

Deliver a notification experience that’s useful, lightweight and doesn’t interrupt user flow as they accomplish their important tasks in our software.

Not included

At this stage, this pattern is limited to on-screen notifications delivered in websites and web apps, rather than through additional alert channels like SMS, Push or email.

User centric

Every notification should be at the ‘user level’ - owned by users and controlled by them. Notifications should feel personal and actionable. It should not be possible for other users or admins to control a users notifications - their state (recency, read/unread) and snooze should be personal to the user and should help them feel in control and feel agency over the system.

Multiple elements

Modularity example