# Edit a select menu

A **select menu** is a dropdown. Members click, the list opens, they pick. The chosen option opens a ticket.

A select menu fills a whole component row. A panel has up to 5 rows, so a panel can have **up to 5 select menus** (one per row). You can also mix select menus with button rows in the same panel.

<figure><img src="/files/neY3Y1BuT7UeYNXtPKAO" alt="A panel in Discord with a select menu open showing multiple options with descriptions and emojis"><figcaption></figcaption></figure>

## When to use a select menu vs buttons

You are not forced to choose a select menu just because you have many options. A panel can hold up to 5 rows of up to 5 buttons, so you can put up to 25 buttons on one panel. A select menu is the better choice when you want a single tidy dropdown instead of a wall of buttons, when your options are closely related and read well as one list, or when each option benefits from a short description under its name.

| Use a select menu when...          | Use buttons when...                       |
| ---------------------------------- | ----------------------------------------- |
| You want one grouped dropdown list | Each option should be visible at a glance |
| The options are closely related    | Some options need visual prominence       |
| Each option needs a description    | A simple label is enough                  |
| You want to keep the panel compact | You only have a few options               |

You can mix the two in the same panel: a Primary button for the most common action plus a select menu for the longer list of topics.

## Select menu fields

### Placeholder

The grey text shown when the dropdown is closed. *"Choose a topic..."*, *"Pick a category"*. Up to **100 characters**.

### Options (the list)

Up to **25 options** per menu.

Each option has:

| Field           | Cap                                                               |
| --------------- | ----------------------------------------------------------------- |
| **Label**       | 100 characters. What members see.                                 |
| **Value**       | 100 characters. Internal identifier (auto-filled from the label). |
| **Description** | 100 characters. Small grey subtitle, optional but recommended.    |
| **Emoji**       | Optional. Same picker as buttons.                                 |
| **Default**     | Toggle. Pre-selected when the dropdown opens.                     |

## Each select-menu option is also an option

Just like buttons, each entry in the select menu has the same set of per-option settings that control what happens when a member picks that option:

* **Option Status.** Enabled or Disabled.
* **Ticket Style.** Text Channel or Thread per option.
* **Support Roles.** Who gets added and (with pings on) pinged.
* **Custom Category.** Where this option's tickets land.
* **Ticket Name Format.** Channel-name format.
* **Custom Embed Content.** A per-option embed shown inside the ticket. Free.
* **Form questions.** Up to 5 questions before the ticket opens.
* **Required Roles / Blocked Roles** (<i class="fa-crown">:crown:</i> Premium). Gate who can use this option.
* **Steam ID Integration** (<i class="fa-crown">:crown:</i> Premium). Require Steam linking first.

For every per-option setting in detail, see:

{% content-ref url="/pages/aHGH6BOJh48aZHUVoiWW" %}
[Per-option settings](/docs/panels/per-option-settings.md)
{% endcontent-ref %}

→ [What option questions are (form questions)](/docs/forms/what-option-questions-are.md)

## Editing a specific option

Click the option in the panel preview to open its editor in the right pane. The per-option settings tabs (General, Messages, Advanced) appear, the same as for button options.

## Adding / removing options

In the panel editor's select-menu section, **+ Add Option** appends a new entry. The red trash icon next to an option removes it.

{% hint style="danger" %}
**Removing an option does not close currently-open tickets** opened from it. Only future ticket openings are affected.
{% endhint %}

## Related

{% content-ref url="/pages/aHGH6BOJh48aZHUVoiWW" %}
[Per-option settings](/docs/panels/per-option-settings.md)
{% endcontent-ref %}

{% content-ref url="/pages/26CaDdu7xwN1Wh12EuWh" %}
[Edit a button](/docs/panels/edit-a-button.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://ticketking.xyz/docs/panels/edit-a-select-menu.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.