> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Banner alert

> Banners are seldom used, but part of our notification and alert ecosystem. They are placed at the top of the UI to show prominent notifications or messages for the product or system, to show a connection issue or to promote a new experience.

## Banner alert

<Badge color="blue">v1.0.0</Badge> | [View in Storybook](https://master--695bb4b1b8041ae09768950a.chromatic.com/?path=/docs/primitives-banner--docs)

Banners are considered high-emphasis communication and should be used sparingly. High-priority feedback is urgent and requires immediate action. These messages are more noticeable and disruptive. They should draw attention or disrupt the user's flow.

### When to use

* Promotion: Use a Banner to promote new features or product offerings.
* Application states: Use a Banner to indicate entire application states such as offline, online, draft state, or edit mode.
* User access: Use a Banner to indicate a user’s access setting, such as view only with the option to request edit rights.

### When to use something else

* Task-specific feedback: Do not use a Banner to provide feedback after a user completed or failed a specific task. Depending on the context, consider inline validation, an [Alert](/aura-design-system/primitives/alert), [Sonner](/aura-design-system/primitives/sonner), or [Dialog](/aura-design-system/primitives/dialog).
* Navigation: Banners should not be used for internal application navigation. Use the top bar pattern and primitives such as [Tabs](/aura-design-system/primitives/tabs) for in-page structure.

### Dos and don'ts

* Do place the Banner at the top of the UI, above the Topbar.
* Don't stack multiple Banners on top of each other.
* Do respect the max height of the Banner, and keep text to a single line.

### Behavior

* High-emphasis, full-width region above primary chrome; may be dismissible or persistent per product rules (including across sessions for announcements).
* Does not trap focus; critical confirmations belong in [Dialog](/aura-design-system/primitives/dialog) or [Alert dialog](/aura-design-system/primitives/alert-dialog).

### Often used with

* Primary or dismiss [Button](/aura-design-system/primitives/button); optional text link; does not replace page [Tabs](/aura-design-system/primitives/tabs) or primary nav.