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

> How Headless keeps Tickets state per server and where to find the guide for each part of the workflow.

Tickets stores each server's configuration and records separately. The panel and its persistent controls are restored after Headless restarts; access to each ticket still follows its private Discord channel permissions.

> [!NOTE]
>
> Channel access determines who can close a ticket or request its transcript. Review the command guide and protect the log channel, which may contain messages and attachment links.

## Explore Tickets

> **[Overview and setup](/docs/en/server/tickets/overview.md)**
>
> Review the supported limits and follow the initial panel setup.

> **[Commands and permissions](/docs/en/server/tickets/commands.md)**
>
> Check access requirements and commands for each actor.

> **[Panels](/docs/en/server/tickets/panels.md)**
>
> Publish the single panel and review its permission diagnostic.

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

> **[Access and privacy](/docs/en/server/tickets/access.md)**
>
> Understand channel permissions and transcript scope.

> **[Lifecycle](/docs/en/server/tickets/lifecycle.md)**
>
> Follow closure effects, retained records, and scheduled deletion.

> **[Messages](/docs/en/server/tickets/messages.md)**
>
> Configure opening, private-channel, closing, and log messages.

> **[Forms](/docs/en/server/tickets/forms.md)**
>
> Review the fixed fields and limits of the initial modal.

> **[Variables](/docs/en/server/tickets/variables.md)**
>
> See which values can appear in Ticket messages.


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