> 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/components/layouts/overlays.md).

# Overlays

Applies to **Classic App Builder**. Start with [Modals and overlays](/classic-app-builder/design-and-structure/components/modal.md) for a complete table-row or button workflow, expected results, and troubleshooting.

Overlays, also known as Modals are windows — both large and small that “pop” onto the screen when an action is taken. Sometimes these come in the form of a warning (e.g. “Are you sure you want to delete that?”) and sometimes they can be in the form of something useful (e.g. clicking a "view details" button and seeing the specifics about an object).

Jet Admin provides 3 types of overlays:

1. Modals. Opens above page content in the center of the screen.
2. Slideouts. Slides outs from the side of the screen over page content.
3. Dropdowns. Dropdown next to click origin over page content.

To set up an `Overlay`, follow the steps:

1. Click on the `Overlays` Tab from the top bar
2. Click `+` on the Add Button near a modal, slideout of dropdown
3. Click on the `Customize` button
4. Choose the Style you want to use

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

You can customize your Modals by showing a close button and enabling closure when clicking the background overlay.

{% content-ref url="/pages/QYoSgofxO9hbUgIdEuFU" %}
[Customizing Overlay](/classic-app-builder/design-and-structure/components/layouts/overlays/customizing-overlay.md)
{% endcontent-ref %}

You can pass dynamic parameters from the page into your Modals, allowing you to populate them with contextual data.

{% content-ref url="/pages/ozdFeSMEriQipiUJ4xj1" %}
[Overlay Parameters](/classic-app-builder/design-and-structure/components/layouts/overlays/overlay-parameters.md)
{% endcontent-ref %}

Modals support adding custom actions, giving you the flexibility to build interactive workflows.

{% content-ref url="/pages/MoIswnfH6a3cjGJ9vuki" %}
[Building dynamic workflows](/classic-app-builder/design-and-structure/components/layouts/overlays/building-dynamic-workflows.md)
{% endcontent-ref %}


---

# 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/components/layouts/overlays.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.