Discord Staff Roles: Permissions and Hierarchy for a Support Team

Most staff setups start with one "Staff" role, half the boxes ticked, given to everyone who helps. It works until a trial helper bans a member by accident or a stolen account pings the whole server. A clear hierarchy prevents both.

What staff roles does a Discord server need?

Short answer: five tiers cover almost every support team. Small servers merge them into three.

Order these roles in Server Settings, Roles, with Admin at the top and Trial at the bottom. That order matters twice. Discord only lets someone manage roles below their own highest role, and a ticket bot can use the same order to decide seniority, as covered below.

Keep support and moderation as separate roles, even when one person holds both. Answering billing tickets well is not the same skill as deciding bans, and Discord roles stack, so each role can stay narrow.

Which Discord permissions are dangerous to hand out?

Short answer: five of them, because each one can do damage that is hard to undo.

If a staff account is stolen, these five are what the thief uses. Keep it simple: only the Admin tier holds Administrator, Manage Server or Manage Roles, only seniors can ban, and nobody on staff needs Mention Everyone for daily work. Discord can also require two-factor authentication for anyone with moderation permissions, which is worth turning on.

The bot's own Discord permissions are a different question, and they have their own guide: ticket bot permissions.

What permissions does a Discord moderator need?

Short answer: Manage Messages, Timeout Members and Kick Members, with View Audit Log so they can see what happened before they arrived.

Timeout is the tool a moderator should reach for first. It is temporary, it stops the problem at once, and a mistake costs someone a few minutes rather than their place in the server. Kick removes someone who can rejoin. Ban is permanent until lifted, which is why many servers keep it with the senior tier.

How do ticket bot staff permissions work?

Short answer: separately from Discord's. In AI Ticket Bot each staff role gets its own set of 15 permissions in four groups, set with /staff roles or on the dashboard.

Three rules sit on top. Manage Server holds all 15, so your Admin tier needs no staff role in the bot at all, and anyone with Administrator counts too. A member with two staff roles gets both sets. And See every ticket is real access: when a ticket opens in channel mode, the bot gives that role the ticket channel, and a role without it does not see the channel at all, unless it is the staff role of that ticket's category.

This is why the Support agent row in the first table needs nothing from Discord: an agent can work a full queue with no moderation power over the rest of your server.

Which bot preset fits each staff role?

Short answer: the bot offers four quick presets, Support agent, Support lead, Moderator and AI trainer. Pick one per role, then adjust.

Four details in that table catch people out.

• The Support agent preset cannot add people to tickets. That sits with Support lead and Moderator. Turn it on for agents if they bring in specialists often.
• The Moderator preset cannot claim. It is built for oversight. If your moderators also answer tickets, give them Claim tickets as well, or a second role.
• The Support agent preset does not have See claimed tickets. An agent loses sight of a ticket while a teammate holds the claim, and gets it back on release. That keeps claimed tickets private by default. Private claimed tickets covers the setting in full.
• Teach the AI is in no support preset. It changes what the AI tells every future member, so give it on purpose. Training an AI ticket bot covers who should hold it.

Can only staff members claim tickets?

Short answer: yes. Claiming needs the Claim tickets permission on a staff role, or Manage Server. Members cannot claim.

Claiming is self-service. Staff pick up the next ticket themselves, first come, and there is no command to assign a ticket to a named person. Seniority comes straight from your Discord role list: someone whose highest staff role sits lower than the claimer's cannot take the ticket over or close it. Manage Server is the exception. What claiming does has the rest.

How many staff roles can you have?

Short answer: the limit counts Discord roles, never people.

Each role holds as many members as you like, so a new helper costs nothing. On Free, three roles fits the merged version: Support agent, Moderator and Support lead, with Admins covered by Manage Server. A Trial tier and an AI trainer role are where a fourth and fifth come from. Current prices are on pricing.

After a downgrade, your oldest roles stay live and the extras are kept but grant nothing until you raise the plan again. How many people to put in each role is a staffing question, answered in support team structure.

Where this setup stops

The last row is the one to take seriously. Ticket permissions sit on top of Discord's, never above them. If the Discord layer is too generous, no bot setting fixes it. Once roles are set, onboarding new moderators covers their first week.