Per-option settings

Every per-option setting on a ticket button or select-menu entry across the General, Messages, and Advanced tabs.

Each button on a ticket panel AND each entry in a select menu is an option. Every option has the same set of settings, regardless of whether it's a button or a select-menu entry. These settings are organized into three tabs: General, Messages, Advanced.

This page covers every option setting. For the visual side (label, color, emoji), see Edit a button or Edit a select menu. The option settings on this page apply to both.

(Application-panel options use a different, flat layout. See Designing your application.)

Header sections (outside tabs)

The per-option editor always shows these sections at the top, regardless of which tab is active:

• Color (buttons only). The Discord button style (Primary, Secondary, Success, Danger). A new button defaults to Secondary (grey). Link buttons have a different editor.

• Actions. Reset and Delete.

• Button Emoji / Option Emoji. Optional emoji.

• Button Text / Option Text. The label (max 80 characters). For select-menu options, an additional description field (max 100 characters).

→ Edit a button

General tab

Field	Description	Type	Is Premium?
Required Roles	Roles the user must have to use this option.	Multi-role, inherit or override	Premium
Blocked Roles	Users with any of these roles cannot use this option. Server-wide blocked roles from your Settings page also block users from every ticket.	Multi-role, inherit or override	Premium
Option Status	Enable or disable this option.	Enabled / Disabled	No (free)
Ticket Style	Override the panel's default ticket style (Text Channel / Thread).	Text Channel / Thread	No (free)

Messages tab

Field	Description	Cap	Is Premium?
Custom Embed Content	Customize the embed shown in the ticket channel.	2048 characters	No (free)
Custom Ticket Message	Custom message sent above the embed when a ticket is created.	1024 characters	No (free)
Admin Thread Message	Message sent in the staff thread (text-channel tickets only). The content only takes effect on Premium.	1024 characters	Premium

Custom Embed Content and Custom Ticket Message both support message variables (see "Variables" below). Steam variables are available when Steam linking is on (Premium).

The Admin Thread Message field is disabled for thread-style options, with the reason "This only works for tickets created as channels, not threads."

Advanced tab

Field	Description	Type	Is Premium?
Support Roles	Roles that can view and manage tickets for this option. Up to 20. Server-wide support roles from your Settings page always apply too.	Multi-role, inherit or override	No (free)
Custom Category	Override the panel default category. Up to 10. Threads cannot have a custom category, so this is disabled for thread options with the reason "This only works for tickets created as channels, threads don't get their own category." Server-wide categories also apply as overflow.	Multi-category, inherit or override	No (free)
Ticket Name Format	Customize the naming pattern for ticket channels. Max 50 characters. The final channel name is capped at 100 characters by Discord.	Text, inherit or override	No (free)
Custom Pings	Configure which roles are pinged when a ticket is created. Toggle "Use ticket roles as ping roles" off to pick specific roles. Disabled for threads.	Toggle + multi-role	Premium
Steam ID Integration	Require members to link their Steam account before opening (toggle "Require Steam Linking").	Toggle, inherit or override	Premium

Variables in template strings

Available in Ticket Name Format, Custom Embed Content, and Custom Ticket Message:

Variable	Resolves to
{TICKET_NUMBER}	The ticket's number
{TYPE}	The panel option label
{USER}	Mention of the ticket author
{USER_ID}	The ticket author's Discord ID
{USER_NAME}	The ticket author's display name
{GUILD_NAME}	Your server name
{CREATED_AT}	Ticket creation time
{STEAM_ID}	Steam ID (only when Steam linking is on, Premium)

In Admin Thread Message ( Premium), additional variables {CHANNEL_NAME} and {CHANNEL_ID} are available.

Variables with no value display as N/A.

Saving

Per-option changes save via the panel's Unsaved Changes Bar. There's no per-option save button.

Validation: missing required fields show animated red borders. Save button stays disabled until validation passes.

Related

Panel-wide defaultsWhat option questions are