> ## 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.

> ## Agent Instructions
> Cognite Data Fusion (CDF) is an industrial DataOps platform. Prefer English docs unless the user asks for another locale.
> Follow /_llms/ index links recursively until you reach page URLs ending in .md. Fetch those Markdown twins instead of HTML.
> For REST APIs, default to calendar version 20230101 (stable). Use 20230101-beta or 20230101-alpha only if the user is on a preview API. Cite paths under /api-reference/concepts/<version>/ and the Cdf-Version header. Prefer the Python SDK (cognite-sdk) unless the user is in JavaScript/TypeScript.
> Start here by task: platform overview /cdf/index.md; data modeling /cdf/dm/index.md; data integration /cdf/integration/index.md; access /cdf/access/index.md; CDF Toolkit /cdf/deploy/cdf_toolkit/index.md; REST quickstart /dev/quickstart.md; Python SDK /dev/sdks/python/index.md; Atlas AI /cdf/atlas_ai/concepts/index.md; Flows apps /cdf/flows/index.md; MCP and IDE setup /dev/guides/ide_ai_integration.md.
> For implementation work, also load /skill.md.

# Banner

> Banners are placed at the top of the UI to show prominent notifications or messages for the product or system, such as promotional features or connectivity issues.

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

## When to use

* Promotion: To promote new features or product offerings.
* Contextual states: To indicate entire application states such as network connectivity issues or trial expiration.
* Persistent feedback: To display messages that should remain visible at the top of a screen until the user dismisses them or resolves the underlying issue.

## 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.
* Permanent content: Banners are temporary and should not be used for core application functionality that belongs in standard headers or sections.
* Critical, blocking alerts: Alerts that must be addressed immediately should be displayed with an [Alert dialog](/aura-design-system/primitives/alert-dialog).

## Dos and don'ts

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

## Behavior

* Banners may be dismissible or persistent per product rules (including across sessions for announcements).
* Banners do not trap focus; critical confirmations belong in [Alert dialog](/aura-design-system/primitives/alert-dialog).

## Often used with

Primary or dismiss [Button](/aura-design-system/primitives/button); optional text link.

## Accessibility

* Landmark structure: Wrap static page-level banners in standard landmark elements like `<aside>` or `<div role="region" aria-label="System Announcement">`.
* Dynamic announcements: For client-side rendered banners, apply `role="status"` so live updates are announced without interrupting active user keyboard flow.