> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/design-and-structure/dropdown-popups.md).

# Dropdown Popups

The Dropdown Popups feature allows you to create interactive dropdown menus that can be triggered by various components such as buttons. This feature enhances user interaction by providing a dynamic way to present additional options or information without navigating away from the current view.

#### Configuration Steps

follow these steps:

1. **Open Overlays**: Navigate to the overlays section of your application.
2. **Create Dropdown Model**: Create a new dropdown model within the overlays section.
3. **Add Action Trigger Component**: Add a component, such as a button, that will trigger the dropdown popup.
4. **Set Action to Open Overlay**: Configure the action of the trigger component to open the overlay and select the newly created dropdown model.

#### Usage

**Scenario: Creating a Dropdown Popup for Additional Details**

In an application, you might want to provide additional details in a dropdown that appears when a button is clicked.

{% @arcade/embed flowId="bJmokGplLc8pMzW5cTAZ" url="<https://app.arcade.software/share/bJmokGplLc8pMzW5cTAZ>" %}


---

# 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://docs.jetadmin.io/classic-app-builder/design-and-structure/dropdown-popups.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.