> ## Documentation Index
> Fetch the complete documentation index at: https://docs.headlesslabs.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Ticket panels

> Publish and update the single Components V2 ticket-opening panel supported for each server.

## Opening panel

The opening panel is published in a text channel selected during setup. It contains an Open ticket button plus the configured media, links, and labels. When pressed, the member completes the configured initial modal and Headless creates a private channel.

> [!NOTE]
>
> Each server stores one panel. `.ticket panel` republishes or updates it at the saved destination; the panel message and persistent controls are restored after Headless restarts. There is no dropdown mode or multiple panels with independent options.

```headless-command Syntax theme={null}
.ticket panel [announce=True]
```

```headless-command Example theme={null}
.ticket panel
```

## Requirements

The actor needs Manage Channels (native or through Headless Fake Permissions). The bot needs native Discord permissions to view and send messages in the panel channel and create/manage channels in the selected category. Setup also checks Manage Roles, Embed Links, Attach Files, and Read Message History; review READY or REVISAR before opening tickets.

```headless-command Syntax theme={null}
.ticket setup <panel_channel> [category]
```

```headless-command Example theme={null}
.ticket setup #support #tickets
```

## Setup steps

**1. Choose the panel channel**

Select a text channel visible to people who should be allowed to open requests.

**2. Choose an optional category**

If provided, Headless creates ticket channels there. Confirm the bot's permissions and category overwrites.

**3. Publish the panel**

Run `.ticket setup #support [#ticket-category]`. Setup enables Tickets, requires the initial reason, and publishes or updates the message.

**4. Test privacy**

Open a test ticket and verify the channel, requester, support roles, and opening message.

> [!WARNING]
>
> Setup may publish the panel even if it reports REVISAR for missing permissions. The result is diagnostic; fix permissions and test private-channel creation before sharing the panel.

## Related pages

> **[Options](/docs/en/server/tickets/options.md)**
>
> Review initial values, effective limits, and Dashboard controls.

> **[Messages](/docs/en/server/tickets/messages.md)**
>
> Configure panel and private-channel text and mentions.

> **[Access and privacy](/docs/en/server/tickets/access.md)**
>
> Check who can view and manage each ticket.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.