Discord Ticket Bot Dashboard: What It Does and Who Can Sign In
Who can sign in to a ticket bot's web dashboard, what your staff get there, what it does that Discord cannot, what stays in Discord, and what members see.
Dani, Founder, AI Ticket Bot
10 min read
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 setup belongs to the people with Manage Server, and the shift gets the same tickets it works in Discord, with the same permissions. 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 that still 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, anyone whose roles give them Manage Server, and anyone with one of your staff roles. You sign in with your Discord account. The dashboard lists the servers where Discord reports you as the owner or as holding Manage Server, and under them, in a group called On the team, the servers where a staff role lets you in. A server where you are neither 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 access that is never more than a minute old, and the bot checks every request a second time against your roles as Discord sees them right then. Take Manage Server or a staff role away from somebody and their dashboard follows within about a minute, even if they stay signed in.
Who gets what on the web
- Owner or Manage Server
- The whole dashboard for that server: tickets, panels, the AI, settings and billing
- A staff role without Manage Server
- What the role allows: the tickets they can see in Discord, closed ones with Read transcripts, asking or teaching the AI, the block list
- A member
- Their own tickets on the account page, and the transcript of any ticket they opened
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:
Only on the dashboard
- Close many tickets at once
- Tick up to 100 open tickets and close them with one shared reason
- Export tickets
- Up to 1,000 as one row each, or up to 100 as a ZIP with every conversation
- The audit log
- Who changed what and when, across tickets, panels, staff roles and settings
- Your website chat
- Set up the chat widget, and answer handed-over chats if you send them to the dashboard
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?
The member's half, and every ping. The ticket page on the dashboard covers what staff do inside a ticket: reply with text or files, send a saved reply, claim it or take it over, rename it, add or remove a person or a role, ping the member, switch the AI off for that ticket, set the priority, move it to another category, ask the member to close, and close it. The five that used to need Discord sit there now, beside their commands:
On the ticket page and in Discord
- Claiming, taking over and unclaiming
- Under Claimed by on the page, or the Claim button and /ticket claim
- Renaming the ticket
- The pencil by its name, or /ticket rename
- Adding or removing a person or a role
- Added to this ticket on the page, or /ticket people
- Nudging the member
- Ping on the page, or /ticket ping: a direct message with an optional note
- Turning the AI off for one ticket
- The AI switch on the page, or /ticket ai
The member's half never moves to the web. 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. Staff can open a ticket for a member from the dashboard's ticket list, as they can with /ticket open. Adding someone to a ticket covers what a person you add can read.
For a moderator this split is convenient: nothing their shift needs is web-only. For anyone working from a browser there is no gap left inside a ticket. What the browser cannot do is tell you something happened, so the pings still land in Discord.
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.
Replying in Discord
- Posted by you, with your name and avatar
- Files and screenshots attach as normal
- @mentions notify as usual
- Reply as Staff with /ticket reply
Replying from the dashboard
- Posted by the bot, starting with your name
- Up to 10 files, 45 MB in all, with up to 1,950 characters
- @mentions show but notify nobody
- Reply as Staff with the switch on the reply box
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. A staff role is the smaller key. It opens the dashboard too, with only what that role allows: the tickets the person can see in Discord and the actions their permissions grant, asking or teaching the AI, and the block list. Panels, settings, statistics, ratings, the audit log and billing stay with Manage Server, whatever the role.
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 in Discord and on the dashboard alike:
Keep Manage Server small
The owner and the one or two people who run the bot's setup: panels, settings, statistics and billing
Give the shift a staff role
In Settings under Team, or with /staff roles in Discord. The default role can claim, close, move and reply
Let leads read transcripts
Tick Read transcripts on their role, so closed tickets, their transcripts and exports open for them on the dashboard
Decide where website chats go
If the chat on your website is on, send handovers to a Discord thread, so someone is pinged
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 someone keeps the Tickets page open. This is the one setting where the dashboard's lack of pings decides how fast a visitor gets an answer. 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:
Where website chats go
- A Discord thread
- A private thread per chat under a channel you choose, with Claim and Close, and a staff role you pick pinged in it
- The dashboard
- The chat waits under Tickets on the dashboard, for Manage Server and for staff with See every ticket and Work on tickets. No thread and no ping
The dashboard option is fine for a small team that keeps the Tickets page open. Its cost is the ping: the dashboard sends no notifications, so a visitor waits until somebody happens to have that page open. And a staff member sees these chats only when their role has both See every ticket and Work on tickets.
Choose the thread and the chat lands where your staff role already gets notified, while anyone who can see the thread 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.
Good fit
- Setting up panels, the AI and your settings on a full screen
- Work across many tickets: bulk close, export, the audit log
- Working a ticket from any browser, a phone included: replies, files, claims and people
Not the right call
- Staff never get panels, settings, statistics, ratings or the audit log, whatever their role
- It never notifies anyone. New tickets and handovers ping in Discord
- A reply's files stop at 45 MB in all. Bigger ones go from Discord
- Members never use it: they open, answer and rate in Discord
- Tickets opened by another ticket bot you connected can be read and answered while open, but the dashboard leaves claiming, renaming, people and closing to that bot
- It is a website, not an app. There is nothing to install
If you want a web inbox login for someone with no Discord role behind it, this is not that. Access follows Discord: give a person a staff role and the dashboard opens for them, take it away and it closes, with no second account to manage. One of our comparisons covers a bot that offers staff sub accounts instead. On a phone, the whole dashboard works in the browser; what changes on mobile covers the rest.
Sources and further reading
Keep reading
Frequently asked questions
On ours, the server owner, anyone whose Discord roles give them Manage Server, and your staff. Everyone signs in with their Discord account. Owners and Manage Server get the whole dashboard; anyone with one of your staff roles gets only what that role allows, on every plan.
Yes, if they have one of your staff roles. They sign in with Discord and get only what their role allows: the tickets they can see in Discord with the actions their permissions grant, asking and teaching the AI, and the block list. Panels, settings, statistics, the audit log and billing stay with Manage Server.
Yes. Type on the ticket page and the bot posts your reply in the ticket, starting with your name, or under a Staff label if you choose to hide it. The member reads it in Discord like any reply. A dashboard reply can carry up to 10 files, 45 MB in all, and an @mention typed in one notifies nobody.
Four jobs have no Discord command: closing up to 100 tickets at once, exporting tickets to a file, reading the audit log, and setting up the chat on your website. Inside a ticket nothing is Discord-only any more: claiming, renaming, adding a person, pinging the member and switching the AI off for one ticket all work on the ticket page too.
No. The dashboard sends no notifications of any kind. Its ticket list refreshes itself every few seconds while it is open, but the pings for new tickets and handovers happen in Discord, so your staff role's Discord notifications are what bring people in.
Ours uses Discord sign-in, so there is no password to create. It asks Discord for two things only: who you are and which servers you are in. It cannot read your messages or act as you in Discord, and losing Manage Server or your staff role in a server closes it to you within about a minute.
Keep reading.
All articlesI Added the Wrong Person, I Mistook You for a Teammate: The Discord Scam
A stranger on Discord says sorry, they added the wrong person and mistook you for a teammate? It opens a scam. What comes next and what to do if you clicked.
8 min read
Discord Support Ticket: How to Submit One, Even When Locked Out
Open a Discord support ticket on the Help Center, even when locked out of Discord: which form fits a hacked account, where your ticket ID is, how long it takes.
8 min read
How to See a Bot's Commands on Discord, on PC and Phone
Type / in the message box to list a bot's commands, or open the App Launcher on PC or phone. Why some are hidden from you, and where admins see every one.
8 min read
See it on your own server.
Add the bot free, teach it a few of your most common answers, and watch it clear the repeat tickets on its own.
Free plan, no card. Premium is free for 14 days once your tickets are live.