Discord Ticket Bot Dashboard: What It Does and Who Can Sign In

Plenty of Discord ticket bots come with a web dashboard. The more useful question is who it is for, because that decides whether your moderators ever open it.

On ours the answer is short: the dashboard belongs to the people who own the setup, and Discord belongs to the shift. This guide covers who can sign in, what the dashboard does that Discord cannot, what stays in Discord, what a member sees when you reply from a browser, and the one setting where that split catches teams out. The same questions are worth asking of any Discord ticket bot with a web panel, because "has a dashboard" can mean a settings page or a second place to work tickets.

Who can sign in to the ticket bot dashboard?

The server owner, and anyone whose roles give them Manage Server. You sign in with your Discord account, and the dashboard lists the servers where Discord reports you as the owner or as holding that permission. A server you cannot manage never appears, and pasting its address in gets you nowhere.

There is no dashboard account to create, so there is none to remove later. Signing in asks Discord for two things: who you are and which servers you are in. No password, no email address, and nothing that lets the site read your messages or act as you inside Discord.

The check is not a one-off at sign-in. Every page and every action asks again, from a copy of your server list that is never more than a minute old, and actions inside a ticket are checked a second time by the bot against your roles as Discord sees them right then. Take Manage Server away from somebody and the server drops out of their dashboard within about a minute, even if they stay signed in.

That last row is why a member can reread their own conversation after the channel is gone, covered in how members find their past tickets.

What does the dashboard do that Discord cannot?

Jobs about many tickets at once, or about records rather than conversations. Discord is very good at one conversation at a time and poor at a list of two hundred. Four jobs have no Discord command at all:

Each has its own guide: closing tickets, exporting them, the audit log and the website chat.

Most of the rest has a Discord twin: panels, settings, staff roles, saved replies, the blocklist, statistics, ratings and teaching the AI. The dashboard version is easier to read and harder to get wrong, because a whole card or list sits on one screen instead of one command reply at a time. For panels that is most of the value, since you edit on a live copy of the post, as panel design shows.

What stays in Discord?

Almost everything the shift does inside a ticket, apart from replying. The ticket page on the dashboard covers the conversation and the decisions around it: reply, send a saved reply, set the priority, move the ticket to another category, ask the member to close, and close it. Five ticket actions are not on it:

The member's half never moves to the web either. A member opens tickets from your panel, answers a close request with its buttons in Discord, and rates a ticket from the direct message sent when it closes. Adding someone to a ticket covers the one of these people most often look for on the dashboard.

For a moderator this split is convenient: nothing their shift needs is web-only. For an admin working from a browser it is a gap, because claiming or renaming a ticket means switching to Discord for a moment.

What does a member see when you reply from the dashboard?

A message from the bot in their ticket, starting with your name. The site has no permission to post as your Discord account, so the bot posts your reply and puts your name in front of it as a mention. That mention pings nobody, you included, and neither does any @mention you type into the reply.

Everything else behaves like a staff reply typed in the channel. It counts toward your numbers in staff statistics, it goes into the transcript under your name (or as Staff), and it counts as your team stepping in: if "Pause the AI when your team steps in" is on in Settings, the AI stands down on that ticket exactly as it would for a reply in Discord. On a chat from your website a staff reply always takes over, whatever that setting says.

The conversation on the ticket page refreshes itself every few seconds, so the member's answer appears without a reload. Anonymous staff replies covers what the Staff label does and does not hide.

Should you give moderators Manage Server for the dashboard?

Usually not. Manage Server is a Discord permission first and a dashboard key second. In Discord it lets someone rename your server, see every invite and add other bots. On the dashboard it unlocks every setting, billing and resetting the AI included. There is no smaller dashboard role to hand out instead, and we do not offer separate staff logins.

The better split keeps Manage Server with the people who own the setup and gives everyone else a staff role, which decides what they can do inside tickets in Discord:

That keeps the dashboard for decisions that affect the whole server, and puts the daily work where your staff already are. How to draw the roles themselves is in how a support team is structured.

Where should chats from your website go?

To a Discord thread, unless only your admins answer them. This is the one setting where the dashboard's gate changes who can do the work. When the AI in your website chat hands a visitor to a person, or when you run the chat with the AI off, the widget page offers two places for those chats:

The dashboard option is fine for a server with one owner doing the support. For a team it has two costs. Only people with Manage Server can open the dashboard, so a moderator without it cannot answer the chat at all. And nothing pings anyone, because the dashboard sends no notifications, so a visitor waits until somebody happens to have the Tickets page open.

Choose the thread and the chat lands where your staff role already gets notified, while an admin can still answer it from the dashboard. The website chat widget covers the rest of its setup.

What the dashboard does not do

The honest list.

If you want every moderator to have their own login to a web inbox with no Discord permission behind it, this is not that. Access follows Discord, which is what makes it simple to run and what makes it impossible to hand out on its own. One of our comparisons covers a bot that does offer staff sub accounts. On a phone, the whole dashboard works in the browser; what changes on mobile covers the rest.