> ## Documentation Index > Fetch the complete documentation index at: https://bettertickets.gg/llms.txt > Use this file to discover all available pages before exploring further. # Settings > Every page in the /ticket edit menu explained in detail: General, Roles, Channels, Voice channels, and Questions, and what each individual field means. `/ticket edit category:` opens an interactive settings menu for one category. It has five pages, switched with a dropdown select menu at the bottom of the message - **General**, **Roles**, **Channels**, **Voice channels**, and **Questions**. Nothing here is a slash-command flag; every field is a button, toggle, or select menu you interact with directly in Discord. This page goes through every field on every page, what it controls, and why you'd change it. ## General Everyday behavior of the category: what members see when their ticket opens, and the limits on who can open one. * **Welcome message**, **button label**, **NSFW**, and **footer text** are all edited together in one modal (click the single "Edit" button under this section): * **Welcome message** - the message posted inside a ticket channel the moment it's created. This is the first thing the ticket's author sees, so it's a good place to set expectations ("a staff member will be with you shortly"). It supports [variables](/docs/variables), including the `{{random: ...}}` tag, so you can rotate between a few different phrasings instead of showing identical text every time. * **Button label** - the text shown on the panel's open-ticket button. * **NSFW** - when enabled, every new ticket channel in this category is created with Discord's age-restricted flag already on, instead of staff having to turn it on per-ticket with `/nsfw`. Useful for categories where restricted content is expected by default. * **Footer text** - a shorter line shown underneath the welcome message, at the bottom of the same block. Commonly used to show who the ticket belongs to (the default footer says who opened it, and who claimed it once claimed) - it also supports [variables](/docs/variables). * **Button style** - the color of the panel's open-ticket button, picked from a separate dropdown right below the button-label field. One of Discord's standard button colors (blue/primary, gray/secondary, green/success, red/danger) - purely visual, doesn't change behavior. * **Per-user ticket limit** - the maximum number of tickets one member can have open in this category at the same time (max 100). Set this to `1` to stop a member from opening a second ticket about the same issue before the first is resolved. * **Staff bypass limit** - when enabled, members with this category's staff roles ignore the per-user ticket limit entirely. Useful if staff need to open test tickets or handle tickets on behalf of many different members without hitting the same cap regular members do. * **Auto delete on leave** - when enabled, a member's open ticket in this category is deleted automatically the moment they leave the server. Without this, their ticket channel stays open (but they can no longer see or reply in it) until staff close it manually. * **Auto close** - automatically closes a ticket if its author hasn't sent a message within a set amount of time (default: 1 hour if you enable it). Useful for categories that get a lot of one-off questions where a non-responsive ticket just needs to be cleaned up rather than sit open indefinitely. * **Check avatar** - when enabled, a member without a profile picture set can't open a ticket in this category. This is a light anti-spam/anti-alt measure, since throwaway accounts often skip setting an avatar. Jail categories only show **Welcome message**, **Footer text**, and **Auto close** on this page. Button label/style, NSFW, per-user limit, staff bypass, auto delete on leave, and check avatar are all hidden, because jail tickets are opened by staff through `/jail`, not by a member clicking a panel - none of those member-facing controls apply. ## Roles Who can manage tickets in this category, who gets notified, and which roles gate access to opening one. Every role list here is capped by your server's premium tier - see the [FAQ](/docs/faq) for the exact numbers per tier. * **Staff roles** - members with any of these roles can claim, close, add/remove members from, rename, and escalate tickets in this category (see [Staff roles vs. server permissions](/docs/tickets/overview#staff-roles-vs-server-permissions) for how this differs from being a server admin). This is the most important role setting on the page - without it, only server admins can manage the category's tickets. * **Ping roles** - roles that get pinged in the ticket channel the moment a new ticket opens in this category. Use this to alert your support team immediately instead of relying on them checking the channel list. * **Required roles** - if set, a member must have at least one of these roles to open a ticket in this category at all. Use this to restrict a category to, for example, verified members only. * **Denied roles** - if set, a member with any of these roles is blocked from opening a ticket in this category, even if they'd otherwise qualify. Use this to stop, for example, a "Muted" or "Banned from support" role from being able to open new tickets. * **Assign roles** - roles automatically given to the ticket's author for as long as their ticket stays open, and removed again when it closes. On a category linked to jail, this list has a different meaning: it's the actual jail role(s) applied to a member when they're jailed with `/jail` (see [Jail](/docs/tickets/jail)). ## Channels Where ticket channels, transcripts, and logs go. * **Open category** *(labeled "Jail Category" for a jail-linked category)* - the Discord category (the folder-like grouping of channels) that new ticket channels are created inside. This is required for tickets to actually open - without it, the bot has nowhere to put the new channel. * **Claim category** - if set, a ticket's channel moves into this Discord category the moment it's claimed, separating "being worked on" tickets from "waiting for staff" ones at a glance in your channel list. If left unset, claimed tickets just stay wherever they already were. Not shown for jail categories, since jail tickets are never claimed. * **Transcript channel** - where the transcript (and its view/download links) gets posted when a ticket in this category closes. Without this set, closing still works, but nowhere gets a copy of the transcript automatically. * **DM transcript to author** - when enabled, the ticket's author also gets the transcript sent to their DMs on close, in addition to (or instead of, if no transcript channel is set) the transcript channel. Useful for categories where the author might want a personal record, like purchase or account-recovery tickets. * **Logging channel** - where open/close/claim/release events get posted as they happen, separate from the transcript itself. Use this if you want an audit trail of ticket activity without every event cluttering the transcript channel. * **Channel name** Premium - a template controlling what generated ticket channels are named, instead of the built-in default. Supports [variables](/docs/variables), including `{% if claimer %}...{% else %}...{% endif %}` so the name itself can change once a ticket is claimed (for example, showing a checkmark and the claimer's name). ## Voice channels Controls an optional button inside open tickets that lets the author (or staff) spin up a temporary voice channel tied to that ticket, for when text isn't enough. * **VC button** - one of three states: **Disabled** (no button shown), **Staff Only** (only staff can create the voice channel), or **Author can request** (the ticket's author can request one, which staff then accept or deny). Pick staff-only if you want to control when voice happens; pick author-can-request if you're fine letting members ask but still want a staff gate before it's created. * **Cooldown per request** Premium - how many seconds must pass before the button can be pressed again, to stop spam-clicking. The built-in default (shown on the page) applies if you're not on a premium tier that allows editing it. * **VC category** - the Discord category requested voice channels are created under. Created voice channels are always deleted automatically when the ticket closes, and their contents (who joined, what was said) aren't logged or included in the transcript. This page isn't shown at all for jail categories - jail tickets never get a voice channel button. ## Questions A list of questions a member has to answer, in one modal, before their ticket channel is created. Use these to collect information up front instead of asking for it manually inside the ticket (e.g. "What's your order number?" before a refund-request ticket even opens). This is more than a plain text box. Each question has its own **input type**, and tickets support eight of them: * **Short text** / **Paragraph** - a single-line or longer free-text answer. Each has its own character-length range you set (up to 250 characters for short, 400 for paragraph). * **Number** - looks like a text field, but is actually validated as a number when the member submits, not just labeled as one. * **Select menu** - up to 25 options you define, shown as a dropdown. You also choose how many the member can pick at once (from 1 up to 8), so it works as either a single-select or a genuine multi-select. * **User** / **Role** / **Channel** - live Discord pickers, not text fields. The member picks real members, roles, or channels straight out of your server's own list instead of typing a name and hoping it matches. Like Select, you control how many they can pick at once, up to 8. * **File** - the member attaches up to 10 files (8MB each). Image and video answers are shown as an inline gallery right in the ticket-open message instead of a plain download link; anything else shows up as a downloadable file. That's the part most ticket bots don't have: asking "which staff member is this about?" or "which channel had the issue?" as an actual picker instead of free text, or collecting evidence as a real question instead of asking someone to drop it in chat after the ticket's already open. Each question also has: * **Label** - the question text shown to the member. (Colons in a label are auto-replaced with semicolons, since `:` is used internally.) * **Required** - whether the member must answer before the ticket can open. A required Select/User/Role/Channel question must allow at least 1 selection. A category can have up to **5 questions**, and that limit isn't premium-gated - it's a hard ceiling because a ticket's whole question set renders in a single Discord modal, and Discord itself caps a modal at 5 fields. Applications don't have this ceiling (see [Application questions](/docs/applications/settings#questions)) because they're asked one at a time in DMs instead of all at once in a modal. This page isn't shown for jail categories, since jail tickets are opened by staff, not through a member-facing question flow.