> 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/structure/panel/panel-tabs.md).

# Panel tabs

Panel tabs display related but specific content within the same panel, filtered views, for example.

<figure><img src="https://1297765105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMoZPkWOmnKvoMWGW4aeM%2Fuploads%2Fkuq4D8sEjdsLGXvV1PrQ%2FPanel%20Tabs%20Hero.png?alt=media&amp;token=4fe9a554-d388-4927-9cfc-7adbd1acacd1" alt=""><figcaption></figcaption></figure>

## Overview

Panel tabs allow switching between different but related content. They're very useful when you need to declutter your interface and make it scannable.

{% hint style="info" %}
**Panel tabs vs Page navigation**

Content update:&#x20;

* Page navigation influences the whole page content
* Panel tabs influence the panel content

Theme consistency:

* Page navigation items don't share any common theme
* Panel tab items share a common theme
  {% endhint %}

## Guidelines

Panel tabs should be used:

* As a quick filter in a [`Datatable`](/design/components/datatable.md) or [`Datalist`](/design/components/datalist.md) context (All orders + Orders in progress)
* As a way to declutter a panel

Panel tabs should not be used:

* For a completion path (use [Stepper](/design/patterns/forms/stepper-form.md) instead)
* For any kind of navigation

Each panel tab can have a specific URL. This is helpful when you have different versions of the same datatable within each tab (with other filters, sorting, or pagination, for example).

Panel tabs always have at least 2 items.

## Content

Tab labels should follow our [content guidelines](/content/writing-for-mirakl.md).&#x20;

Labels must be as concise and precise, with no more than 2 words.

<br>


---

# 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/structure/panel/panel-tabs.md?ask=<question>&goal=<user_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.