When one admin handles every ticket, access isn’t a question. Once three to five people share support and the topics vary — reports, billing, tech issues — the awkward questions start. Should moderators see billing tickets? Who gets to close a report? Who can edit the panel, and who should only reply?
Here’s how to split your team into roles so everyone sees their own work, nobody steps on anyone’s toes, and settings don’t break from a stray click.
Working tickets and configuring them are different kinds of access
Start by separating two levels.
- Working tickets — seeing them, replying, claiming, closing. This happens in Discord and is controlled by topic roles.
- Configuration — panels, topics, forms, other people’s permissions. This is the web dashboard and its Access tab.
Most staff only need the first level. The second belongs to the two or three people responsible for how support is set up. Mix them and you get a familiar story: someone was given Manage Server so they could answer tickets, and along with it they got the power to change settings for the entire server.
Staff roles per topic
Create roles for functions, not for individual people: Support, Moderation, Billing, Recruitment. People come and go, the role stays, and you don’t have to reconfigure topics.
In Discord Tickets every topic has an Admin roles field. Roles on that list:
- get access to the topic’s tickets — a ticket channel is visible only to the opener and the topic’s roles;
- are mentioned when a ticket opens;
- can close the topic’s tickets, if the panel allows it (more on that below).
A sample layout for a four-topic menu:
| Topic | Admin roles | Who sees the ticket |
|---|---|---|
| Technical issue | Support | The opener and support |
| Report a member | Moderation | The opener and moderators |
| Billing question | Billing | The opener and two or three billing staff |
| Join the team | Recruitment, Senior Mod | The opener and the decision makers |
Mind the mention on open. Put a 40-person role on a topic and every ticket pings all forty of them. Within a week they mute notifications, and the ping stops doing its job. Use narrow working roles for topics rather than one big Moderator role for the whole team.
Tip. A role can sit on several topics. Give your support lead a dedicated role and add it to every topic: the lead sees everything, while frontline staff see only their own area.
Default roles
To avoid adding the base role to every new topic by hand, set it once under Settings → Default staff roles. These roles are filled into new topics automatically, and you can then adjust the list on any specific topic — drop what isn’t needed or add a narrow role.
A setup that works: make the support lead role the default and add frontline roles to topics as needed. That way a new topic never ends up unattended, even if someone created it in a hurry.
Blocked roles on a topic
The flip side of access is who can’t open a topic. Every topic has Blocked roles: a member with any of them can’t open that topic, though other topics stay available.
Where it helps:
- Join the team is blocked for Moderation — current staff have no reason to apply;
- Billing question is blocked for Unverified — verification comes first;
- Partnership request is blocked for Newcomer — let them look around first.
This is a block on a single topic. To shut someone out of tickets across the whole server, you have Ticket-banned roles and the /ticket ban command — covered in our article on stopping ticket spam.
Who can close tickets
Who can close is set for the whole panel under Advanced settings. There are three options.
| Option | When it fits |
|---|---|
| Opener or admins (default) | Regular support: members close the ticket themselves once the issue is solved |
| Admins only | Reports, applications, disputes: the team decides, and the opener shouldn’t close a ticket mid-review |
| Opener only | Rare cases where the member should close it as confirmation the issue is solved |
Admins only has one more upside: quick close reasons work when only admins can close and a reason is required. If you plan to track why tickets close, decide this up front — see close reasons and support metrics.
To keep two people from answering the same ticket at once, use the Claim button under the welcome message. An admin claims the ticket, the message shows Claimed by and a Close ticket button appears. Everyone else can see it’s taken.
Dashboard access: the Access tab
The web dashboard opens only for people who have Manage Server or Administrator on the server. The server owner has every permission. Anyone else with Manage Server and no separate entry gets Panels and Transcripts.
In the Access tab you grant permissions to a specific member or to a whole role:
| Permission | What it covers |
|---|---|
| Panels | Panels, topics, publishing, server settings |
| Transcripts | Ticket history |
| /ticket ban | The command that stops a member from opening tickets |
| Access | Granting and revoking permissions for others |
One detail matters here: /ticket ban is available to anyone with that permission in the Access tab, or with the Discord permission Manage Roles. So a moderator doesn’t need Manage Server to stop ticket spammers — grant them /ticket ban and they use the command right in Discord.
A typical layout:
| Who | In Discord | In the dashboard |
|---|---|---|
| Owner | Server owner | Everything |
| Support lead | Manage Server | Panels, Transcripts, Access |
| Server admin | Manage Server | Panels, Transcripts |
| Moderator | Working topic role | /ticket ban |
| Support staff | Working topic role | Nothing, works in Discord |
Least privilege
Everyone gets exactly what their job needs and nothing on top. A checklist:
- Permissions fit the task. Answering tickets — a topic role. Stopping spammers —
/ticket ban. Editing panels — Panels. - Don’t hand out Manage Server for tickets. It’s a server-wide Discord permission, not a ticket one, and it grants far more than answering requires.
- Access goes to one or two people. Whoever grants permissions can grant them to anyone, themselves included.
- Roles for the team, individual entries for exceptions. When someone leaves, remove the role and their access is gone everywhere. Keep per-member entries for one-off cases.
- Sensitive topics get a narrow role. Billing, reports about staff, appeals — two or three people, not the whole team.
- Review regularly. Every month or two, go through the Access tab and your working roles. Former moderators with live permissions are a common gap.
- The bot gets only what it needs, too. Which permissions a ticket bot needs and why is covered in ticket bot permissions.
Step-by-step setup for topic roles and dashboard permissions is in the docs: see Topics and Access for your team.