Notification Center

Triage product, team, and account notifications by priority, source, and read state without losing important updates. This example brings All and Mentions together so team members can find the next task without losing context.

It includes representative records such as You were mentioned in onboarding spec and Deal reassigned to your team. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Notification Center
Use this template in Figr

Template facts

Screen

Inbox

Primary action

Mark all read

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to mark all read while keeping unread, mentions and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: All gives users an obvious place to start.
  • Supporting view: Mentions keeps the related context close.
  • Primary action: Mark all read stays visible when people need it.
  • First signal: Unread shows a useful value (31).
  • Second signal: Mentions gives additional context (8).
  • Sample record: You were mentioned in onboarding spec.
  • Next record: Deal reassigned to your team.

States worth designing

  • No items match the selected filter: say what changed, protect progress, and offer a clear next step.
  • Message or task loading: say what changed, protect progress, and offer a clear next step.
  • Reply or assignment failed: say what changed, protect progress, and offer a clear next step.
  • Item resolved: say what changed, protect progress, and offer a clear next step.
  • Escalation required: say what changed, protect progress, and offer a clear next step.
  • Permission to read restricted content missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

All → Mentions → Mark all read → Review outcome

Patterns used

Inbox, All, Mentions, contextual actions, error recovery

Why these choices work

Keep the current item close to its history, owner and urgency. Put the next action on the record rather than making people open several panels.

Pay attention to all and mentions. People need to distinguish You were mentioned in onboarding spec from Deal reassigned to your team. Keep unread visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Mark all read”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Announcement Composer, Shared Inbox Rules, Message Search.

Start from this in Figr

Design a notification center screen inside our existing product. Use our current components, tokens and content language. Include All and Mentions views, credible records like You were mentioned in onboarding spec, and a clear “Mark all read” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr