> ## 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 access

> Requester, Headless, support-role, and log-channel permissions verified against real private-channel creation.

Headless sets channel overwrites when each ticket is created. Effective privacy depends on those overwrites, the bot's native Discord permissions, and the selected category.

## Private-channel access

* **`@everyone`** — **Applied access:** Denied `View Channel`.
* **Requester** — **Applied access:** Can view and send messages, read history, and attach files.
* **Headless** — **Applied access:** Needs to view and send messages, manage channels, read history, and manage the required overwrites.
* **Support roles** — **Applied access:** Can view the channel, send messages, read history, and manage messages. Up to 25 roles are supported per server.

The support role grants access to staff actions. Claiming requires a configured support role or `Manage Channels`. Configure the support role with `.ticket role <role>`. The actor check for Ticket configuration accepts native `Manage Channels` or the corresponding configured Fake Permission; that does not grant Discord permissions to the bot.

```headless-command Syntax theme={null}
.ticket role <role>
```

```headless-command Example theme={null}
.ticket role @Support
```

## Bot permissions and setup diagnostics

`.ticket setup` checks `View Channel`, `Send Messages`, `Manage Channels`, `Manage Roles`, `Embed Links`, `Attach Files`, and `Read Message History`. The command may publish even when the result is `REVISAR`; resolve permissions in both the panel channel and category before making the panel public. Discord's API remains authoritative for each operation.

> [!WARNING]
>
> A ticket category may also contain overwrites that change inherited access. Test a created channel with a requester and a support account; do not infer privacy solely from the support-role list on this page.

## Log channel and data privacy

Transcripts and logs are sent only to the channel explicitly set with `.ticket log #channel`. There is no automatic fallback. A text transcript may contain recent messages, message IDs, authors, timestamps, content, and links to up to eight attachments per message. Restrict that channel to authorized staff and apply your server's retention policy.

```headless-command Syntax theme={null}
.ticket log <channel>
```

```headless-command Example theme={null}
.ticket log #ticket-logs
```

## Not available

Headless has no ticket blacklist, manual `allow`/`deny` commands, or action for adding extra participants. Adding a support role grants the server-wide support access to tickets; it is not a per-channel participant list.

## Related pages

* [Commands and permissions](/docs/en/server/tickets/commands.md)
* [Ticket lifecycle](/docs/en/server/tickets/lifecycle.md)
* [Headless permissions](/docs/en/permissions.md)


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