Overview
Use NotificationCenter as a persistent inbox for relevant notices that people may need to review, act on, or revisit.
Workspace notifications
Notifications
1 unread
- Unread
Anatomy
The center combines unread summary and filtering with notices that expose priority, content, metadata, and actions.
- 1Unread summary
States pending attention.
- 2Bulk action
Marks visible notices read.
- 3Filter
Switches all and unread views.
- 4Notification content
Explains event and context.
- 5Notice action
Opens the relevant workflow.
When to use
Use NotificationCenter for attention management where notices need tracking and action.
Recommended
- Collect asynchronous notices
Keep updates available after they arrive.
- Support follow-up actions
Link directly to relevant work.
- Manage attention
Track read and unread state.
When not to use
NotificationCenter should be reserved for actionable updates that need triage.
Avoid
- Do not use for inline feedback
Use Alert or Toast.
- Do not narrate all collaboration
Use ActivityFeed.
- Do not store immutable evidence
Use AuditLog.
Variants
Outlined
Bounded inbox.
Filled
Tonal panel.
Raised
Popover-style center.
Density
Three item sizes.
States
| State | Trigger | Visual response | Interaction |
|---|---|---|---|
| Unread | ID absent from readIds | Tonal item and indicator | Open or act |
| Read | ID in readIds | Standard item | Can revisit |
| Filtered | Unread selected | Unread notices only | Switch filter |
| All caught up | No unread notices | Positive empty message | Return to all |
| Loading | Fetch in progress | Status | Wait |
Behavior
Opening or acting can be tied to read-state transitions while filtering remains internal to the collection.
Read state
Opening or acting marks a notice read.
Filtering
All and unread views preserve the collection.
Bulk read
Marks every current notice as read.
Actions
Host owns navigation and mutation.
Accessibility
| Key | Action |
|---|---|
| Tab | Moves through filters, notices, and actions. |
| EnterSpace | Opens, acts on, dismisses, or filters. |
- Announce the unread count politely.
- Expose active filters with aria-pressed.
- State unread status in text.
- Give dismissal controls notice-specific names.
- Keep item and secondary actions separate.
Content guidelines
Keep each notice concise, with outcome, impact, and next action.
Lead with the outcome
State what changed clearly.
Access request approved
Add actionable context
Explain impact or next step.
Review payment details before renewal.
Name direct actions
Use concise verbs.
Review, Open, Dismiss
Use categories consistently
Identify product domain.
Security
Examples
Use an empty-state section for teams with catch-up workflows.
All caught up
Props / API
NotificationCenter extends section attributes.
Props