pattern-library checked
Carbon Design System Notifications Pattern
Documents notification status and type choices, including banner notifications as product or system level messages that persist at the top of the related content area until dismissed.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Banner | Choose banner when the message scope spans multiple pages, sections, records, or sessions in the same product, service, account, or workspace. | The banner appears before users encounter content affected by the message. | Carbon distinguishes banners as product or system-level messages that sit at the top of the related content area, persist until dismissed, and should not cover content. |
| Notification banner | Choose notification banner when a service message should be seen immediately before the page heading and before users interpret that page. | The banner appears before the page H1 and in the same content width as the heading and body text. | Carbon notification guidance supports matching notification type and disruptiveness to user goal, urgency, context, persistence, and next-step clarity. |
| Notification center | Choose notification center when messages must be revisitable after toast, push, email, or inline surfaces have disappeared. | The entry point opens the notification center without navigating away from the current task unless the product uses a dedicated full page. | Carbon describes notification panels as user-opened centers for system-generated messages and recommends chronological ordering, grouping, preferences, and avoiding repeated notifications. |
Evidence Role
This source is treated as pattern-library evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: IBM Carbon Design System. Last checked: .