> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/design/components/actions/contextual-toolbar.md). # Contextual Toolbar Convert a single page into a dynamic interface by granting users efficient control for visualizing and managing displayed data.

The **Contextual Toolbar** is a versatile component designed to let users managing the context of data on a page efficiently. Integrating [pickers](/design/components/form/pickers.md) and filters, it provides users a granular control over the displayed information and transform a single page into a dynamic interface. ## When to use Contextual Toolbar is useful for interface displaying multiple data, such as dashboards or complex DataTables or DataLists. It differs from simple filters as it enables the display of the same items but with different data attached, depending on the context. Below is an example of how the same DataTable with and without a Contextual Toolbar. The use of the toolbar enhances readability by eliminating a column (channel) and concatenating multiple rows (items).

## How to use ? Contextual Toolbar is a versatile component. From a technical point of view, it can be used freely : at a page level, in a panel or in a card. When used alongside a DataTable or DataList with integrated toolbars, the Contextual Toolbar should avoid replicating identical filters, maintaining separate functionalities. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://design.mirakl.com/design/components/actions/contextual-toolbar.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.