Guide · 7 minutes

How to restrict Discord tickets to specific roles

A refund request does not belong in front of every moderator. A partnership offer should reach the people who decide on partnerships, not the whole support team. Here is how to keep each kind of ticket with the team that handles it in SUPREO, give supervisors a read-only view, and check who sees what before a member's private details end up in the wrong channel.

Why restrict tickets at all

Giving every staff role every ticket works for a small server with one team. As soon as you have several, it causes three problems:

Privacy. Billing tickets carry order numbers and emails; reports name the member being reported. Fewer eyes on them is better for everyone.
Noise. A support agent scrolling past partnership requests and staff applications they cannot act on answers the tickets they can act on more slowly.
Accountability. When a ticket can only be handled by one team, it is clear whose job it is, and it does not sit unanswered because everyone assumed someone else would take it.

How ticket access works

Access is decided at three levels, and the most specific one wins:

Category — "Billing" inside your Support panel can be kept to your accounting role.
Panel — your whole "Partnerships" panel can be kept to your partnership managers.
Server — everything else goes to the staff roles on the Roles page, as before.

Each role you add either handles the tickets — sees the channel, replies, claims, closes, writes notes — or is read only: it sees the channel and the transcript but cannot write or use the ticket's buttons.

The admin group on the Roles page, Discord administrators and the server owner always see every ticket. You cannot lock yourself out by mistake.

Before you start

SUPREO on your server with at least one ticket panel. If you have none yet, set up a ticket bot first — it takes ten minutes.
One Discord role per team: Support, Billing, Partnerships… Ticket access uses the roles you already have; it does not create any.
Manage Server on the server, to open the dashboard.

The setup, step by step

Map out who should see what

Before clicking anything, write it down. One line per panel and category, the team that handles it, and anyone who should only read it. A typical community server ends up with something like:

Support → General help: Support team.
Support → Billing: Billing team; Support lead reads.
Support → Report a member: Moderators; Trainee mods read.
Partnerships panel: Partnership managers.

Whatever is not on your list stays with your general staff.

Restrict a panel

On the dashboard, open Ticket Panels, pick the panel and go to its Access tab. Choose Only these roles and add the roles that handle its tickets. Save.

From now on, a ticket opened from that panel is visible to those roles only — plus your admins. The tab also lists the categories of the panel that have a rule of their own.

Narrow a category

Still on the panel, open the Categories tab and click a category. Under Who handles these tickets, choose Only these roles and add its team. Left on Same as the panel, a category follows its panel.

The role pinged when a ticket opens is a separate setting just above it, Role to ping. Usually it is one of the roles that handle the category.

Add read-only roles where useful

Next to each role, switch Handle to Read only for people who should follow tickets without acting on them: a team lead reviewing how billing is handled, or trainee moderators learning from real reports. They see the channel and its history, and the bot refuses them the buttons — they cannot close, rename or reply.

Check the result

Open Ticket Access in the sidebar. The table lists every panel and category with the roles that handle it, and where the rule comes from: the server's staff, the panel, or the category itself.

Check access answers the question you will be asked first: "can the support team see billing tickets?" Pick a role, and you see every kind of ticket it sees, and whether it handles or only reads it.

Update tickets already open

Rules apply to tickets opened after you save them. Tickets already open keep the access they had — on purpose, so nobody loses a conversation half-way. When you are ready, press Apply to open tickets on the Ticket Access page, and their channels follow the new rules.

Test with a second account

From an account that is not staff, open a ticket from a restricted category, then check:

The roles you chose see the channel; your general support role does not.
A read-only role sees the messages but cannot type, and the ticket's buttons tell it so.
On the dashboard, an agent without one of those roles does not see the ticket in Open Tickets.

Three setups that work well

Community server with a store

A single Support panel; the Billing category kept to the billing team, with the support lead read only. Everything else stays with support.

Esports or creator team

A separate Business panel for sponsorships and collaborations, kept to the management role, so offers and prices never reach the moderators.

Large server with a moderation team

The Report a member category kept to moderators, trainees read only. Reports stay out of sight of general helpers, and new moderators learn on real cases without acting on them.

On the dashboard too

The same rules follow tickets onto the dashboard. Agents and log viewers only see a restricted ticket — in Open Tickets, history, transcripts and attachments — when they hold one of its roles, and a read-only role sees the conversation without the reply box. The allowed roles are saved on each ticket when it opens, so its history keeps the same access even if you change the rules later.

Restricting a panel is free. Restricting a category, the read-only level and Check access are part of Premium. See pricing.

When something does not work

A team still sees tickets it should not. The ticket was opened before you saved the rule. Press Apply to open tickets. If the role has Discord's Administrator permission, it sees every channel whatever the rules say.
Nobody but admins sees a category's tickets. It is set to Only these roles with no role in the list. Add one.
A read-only member can still type. Another role of theirs handles the ticket, or has Discord's Administrator permission. The highest access wins.

The full reference is in the docs: ticket access, ticket panels and roles & access. Still stuck? Ask on the SUPREO support server.

Frequently asked questions

Can I hide some tickets from my general support team?

Yes. Set the panel or the category to Only these roles and leave the support role out. Your support team keeps every other ticket, and no longer sees those.

Do admins lose access to restricted tickets?

No. The admin group on the Roles page, Discord administrators and the server owner always see every ticket. On the dashboard, members with Manage Server see them all too, so nobody can lock themselves out.

What happens to tickets that are already open when I change the rules?

Nothing until you press Apply to open tickets on the Ticket Access page. New rules apply to new tickets; the button updates the channels of tickets already open.

Does the member who opened the ticket still see it?

Always. Access rules only decide which staff roles see a ticket. The member who opened it, and members added to it, keep their access.

Does it work for DM tickets and a separate support server?

Yes. The same rules apply, using the support server's roles when tickets are routed there.

Is a restricted ticket hidden on the dashboard too?

Yes. Agents and log viewers only see the open tickets, history, transcripts and attachments of a restricted ticket when they hold one of its roles. A read-only role sees the conversation without the reply box.

Give every ticket the right team

Add the bot, sign in with Discord, and keep each kind of ticket with the people who should handle it.

Moderating too? Read how to set up moderation on Discord.