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

# Activable Panel

A Panel variant with dynamic display control to bring flexibility in the interface.

<figure><img src="https://1297765105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMoZPkWOmnKvoMWGW4aeM%2Fuploads%2FTHXP4sDqiGZ0mzOnzr6F%2FActivable%20Panel%20Hero.png?alt=media&amp;token=10cd1be1-3596-43c6-89a7-9142d84beb4d" alt=""><figcaption></figcaption></figure>

## Overview

Activable Panels are dynamic component used to display or hide elements based on user interactions.

Each panel includes a title and a mandatory switch button (with an attached label), allowing users to easily control what they see.

## Guidelines

1. **Toggling On Displays Content:** When the switch is activated, additional content or features become visible.
2. **Toggling On Hides Content:** When the switch is activated, certain content or features are hidden to simplify the view.

## Content

* **Clarity is Key:** Ensure that the label on the Switch Button is exceptionally clear. Users should understand exactly what will happen when they toggle the switch—whether it will reveal or hide information.

{% hint style="info" %}
Learn more about how to use Activable Panel in [Configure Options ](/design/patterns/configure-options.md)Pattern.
{% endhint %}


---

# 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/activable-panel.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.