One of the first calls you make when setting up tickets is where they live. There are two options: the bot creates a separate private channel for every request, or a private thread inside a single channel. Both work, but they look different to members and staff, behave differently on close and need different bot permissions.
Below we compare them point by point and suggest which mode fits which job. If you don’t have tickets yet, start with the step-by-step setup guide.
How each mode works
Private channel
The bot creates a new text channel in the chosen category and sets permissions so only the opener and the topic’s admin roles can see it. For everyone else, the channel doesn’t exist. The name comes from a template like ticket-{counter} or ticket-{username}.
Private thread
The bot creates a private thread in the parent channel. No new channel shows up in the list: the ticket lives inside the parent channel as a conversation within it. Members only see their own thread, not anyone else’s.
Tip. Threads inherit permissions from the parent channel. Members need to see that channel and have Send Messages in Threads there, or they won’t be able to write in their ticket. They don’t need to post in the parent channel itself — you can keep it read-only.
Side-by-side comparison
| Private channel | Private thread | |
|---|---|---|
| Created in | The chosen category | The parent channel |
| Channel list | Every ticket is a new channel | Stays the same, tickets sit inside one channel |
| Who can see it | Opener and the topic’s admin roles | Opener, topic roles and anyone with Manage Threads in the parent channel |
| On close | Deleted or kept as a read-only archive | Locked and kept as an archive |
| Delete the channel on close | Applies | Doesn’t apply |
| Bot permissions for the mode | Manage Channels, Manage Roles | Manage Threads, Create Private Threads, Send Messages in Threads |
| Best for | Serious, longer requests | Frequent short questions |
Visibility: who sees a ticket
In channel mode, access is set by permissions on that specific channel. The bot opens it to the opener and the topic’s admin roles, and nobody else. That means every topic can have its own staff circle: moderators see reports, admins see staff applications, and the two groups don’t overlap.
Thread mode has a catch. Discord shows every private thread in a channel to anyone with Manage Threads in the parent channel. If your moderator role has that permission server-wide, they’ll see all thread tickets, including topics that aren’t theirs. Before switching to threads, check who has Manage Threads and remove it in the parent channel where needed. We cover splitting access inside a team in support team roles and access.
In both modes, members with the Discord Administrator permission see everything — keep that in mind when handing out roles.
Archives and deletion
A channel can go two ways on close:
- Delete the channel on close is on — the channel is deleted along with the conversation. The list stays clean, but the conversation is gone from Discord for good.
- It’s off (the default) — the channel stays in the same category as a read-only archive. You can come back to it, but closed channels pile up over time and the category needs regular cleanup.
A thread gets locked on close and stays as an archive in the parent channel. Delete the channel on close doesn’t apply to threads. A closed thread stays out of the way yet within reach: you can find it in the parent channel’s thread list.
Whichever mode you pick, the Tickets tab in the dashboard keeps a card for every request: who opened and closed it, when, first response time, duration and close reason.
Channel list clutter
With channels, every open ticket is a separate line in the category. Staff see all open tickets as a list right in the Discord sidebar, which is handy while there are only a few. Once there are dozens, plus archives piling up next to them, the category turns into a long scroll. Members only see their own channel.
With threads, the channel list doesn’t change at all. Tickets are grouped inside one parent channel, and the server looks as tidy as it did before you launched support. For large servers with a steady stream of similar questions, that’s a real plus.
When to use which
Go with private channels if:
- requests are serious and take a while: reports, appeals, staff applications;
- you need tight control over who sees each topic’s tickets;
- you want tickets deleted after they’re closed;
- your team likes seeing open tickets as a list in the category.
Go with private threads if:
- you get lots of short questions;
- the server is big and you don’t want the channel list to balloon;
- closed tickets should stay at hand as an archive;
- only people allowed to see every ticket have Manage Threads in the parent channel.
You can use both
In Discord Tickets, the mode is set with the panel’s Opens as setting — one choice for the whole panel. You can have up to three panels per server, so mixing modes is easy. For example:
- a Support panel — private threads in
#questions, quick answers without extra channels; - a Reports and applications panel — private channels in a separate category, visible only to moderators and admins.
Each panel has its own log channel, so you can send different queues to different log channels.
Tip. Whatever mode you choose, the bot needs View Channel everywhere it works: the ticket category or parent channel, the panel channel and the log channel. Starting November 16, 2026, Discord fully hides channels a bot can’t view from that bot. For the rest of what the bot needs and why, see ticket bot permissions.
Every panel field, including Opens as, Category and Parent channel, is described in the panel docs.