> For the complete documentation index, see [llms.txt](https://docs.tickettool.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tickettool.xyz/beta-docs/dashboard/panel-configs/dropdown-style.md).

# DropDown Style

To access these settings:

> Head to your [Dashboard](https://tickettool.xyz/manage-servers)\
> Select your server\
> Go to the [**Panel Configs**](/beta-docs/dashboard/panel-configs.md) Tab\
> Under **Panel Settings**, click on **DropDown Style** Options

Dropdowns allow you to display several panels in the same select menu.

![Dropdown Style Options](https://i.imgur.com/piFUiPr.png)

### Enable Select Style

In order to use dropwdons instead of [panel buttons](/beta-docs/dashboard/panel-configs/panel-options.md) this option must be on, otherwise regardless the rest of settings of the menu, buttons will be still used.

### Dropdown Editor

#### Display

The shown text on the select option, this is a **required** field.

#### Panel

The panel this option should open a ticket for, this is a **required** field.

{% hint style="danger" %}
Do **not** select twice the same panel, each option needs its own panel.
{% endhint %}

#### Emoji

The emoji that the option should be displayed, leave this field empty for no emoji.

#### Description

The text shown below the Display on the select option, leave this field empty for no description.

#### Placeholder Text

The text the select menu will display before selecting a panel option.

### Cheatsheet

For a clearer view of what a single panel looks like both in your Dashboard and Discord check the following example:

![Dashboard View](https://i.imgur.com/Hxm09wq.png) ![Discord Result](https://i.imgur.com/WBB8eDb.png)

{% hint style="success" %}
Make sure to always **save** changes using the pop-up shown whenever a change is done.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tickettool.xyz/beta-docs/dashboard/panel-configs/dropdown-style.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.