Installation

Create a Discord application, enable the required intents, connect the token to TicketCord, and invite the bot with the right permissions

TicketCord runs your own Discord bot: you create the application in Discord's Developer Portal, and TicketCord runs it under your name and avatar. This page walks through every step, from an empty Developer Portal to a bot that is online in your server.

You need a Discord account, and Administrator (or ownership) on the server you want to add the bot to. Discord itself also requires Manage Server to add any bot to a server.

Step 1: Create the Discord application

Open the Developer Portal

Go to discord.dev and sign in with the Discord account that should own the bot.

Create a new application

Click New Application, enter the name you want your bot to have, accept the terms, and click Create. You can change the name and avatar later; TicketCord reads both from Discord.

Turn off Public Bot

Open the Bot tab. Find Public Bot and switch it off (the toggle turns grey). This stops strangers from adding your bot to their servers.

If Discord refuses with "Private application cannot have a default authorization link", open the Installation tab, set Install Link to None, save, and switch Public Bot off again. TicketCord builds its own invite link, so the default one is not needed.

Leave Requires OAuth2 Code Grant off. When it is on, Discord blocks the invite with "Integration requires code grant".

Leave the privileged intents to TicketCord

TicketCord needs Server Members Intent and Message Content Intent (under Privileged Gateway Intents on the Bot tab) to see who joins or leaves, verify staff roles, and read ticket messages for transcripts, ModMail, and AI features. You do not need to turn them on: TicketCord switches both on for you when it checks your token.

Discord refuses that for a bot whose servers have more than 10,000 members together until it approves the intents. The token check then says the intents are off: apply for them here (Discord's approval is needed first for such a bot), turn both on once approved, save, and check the token again. If an online bot is turned away later with a "disallowed intent" error (code 4014), TicketCord tries once more, and if the bot still cannot connect, turn them on manually and press Restart on the bot's Bot profile page in the dashboard.

Do not turn these off later. The bot goes offline until they are enabled again.

Copy the bot token

Click Reset Token, confirm, and copy the token. This is the only credential TicketCord needs; the application ID is read from it. You do not need the Client ID or Client Secret.

Treat the token like a password. Anyone who has it controls your bot. Discord shows it only once; if you lose it, reset it again.

Step 2: Connect the bot to TicketCord

Go to Add a bot Go to Invite to a server

Sign in to the dashboard

Open ticketcord.com/dashboard and sign in with Discord.

Add the bot

The first time you sign in, a guided setup opens. Click Get started and paste the token on Connect your bot. Otherwise, go to Add a bot, under Your bots in the sidebar, and paste the token into Bot token. The page shows three steps: Paste your token, Check your bot, and Done.

Check and connect

Click Check token in the guided setup, or Continue on the Add a bot page. TicketCord checks the token, connects to Discord once, and shows the bot's name and avatar.

If the check says the privileged intents are off (Discord would not turn them on for the bot), go back to the Developer Portal, enable both intents, and check the token again.

If the name and picture are right, click Connect bot (guided setup) or Add this bot. The bot starts within a few moments and shows as online in the dashboard.

Invite the bot to your server

In the guided setup, press Add bot next to your server on Add your bot to a server. and approve it in Discord.

Outside the guided setup, the Add a bot page lists your servers with an Invite button right after the bot is added. Later, use the Add TicketCord to another server tile on the dashboard home, or open the bot (under Your bots in the sidebar) and use Invite to a server.

The invite link requests exactly the permissions listed below plus the applications.commands scope that registers the slash commands.

Every new TicketCord account starts a 14-day Enterprise trial with no card required, so every feature is available while you set up. When the trial ends, the account moves to the Free plan; nothing you configured is deleted.

Permissions the invite requests

PermissionWhy the bot needs it
AdministratorWork in every channel and category you pick, whatever their permission overrides (see below; you can untick it)
View ChannelSee the channels and categories it works in
Manage ChannelsCreate, rename, move, and delete ticket channels, and create the ticket categories and staff channels when you ask it to
Manage RolesSet per-ticket permission overwrites for the creator and staff, and create the staff roles when you ask it to
Manage WebhooksDeliver logs and transcripts
Send MessagesPost ticket messages, panels, and replies
Send Messages in ThreadsReply in thread-style tickets
Create Public ThreadsOpen thread-style tickets
Create Private ThreadsOpen private thread-style tickets
Manage ThreadsArchive, rename, and delete thread tickets
Manage MessagesPin panels and clean up ticket messages
Pin MessagesPin the welcome message in tickets
Embed LinksSend rich embeds and panels
Attach FilesSend transcripts and attachments
Read Message HistoryRead ticket conversations for transcripts and AI
Add ReactionsAdd reactions to messages
Mention EveryonePing staff roles when a ticket opens
Use Application CommandsRegister and run slash commands

Why the invite asks for Administrator

Since October 2026 the invite asks for Administrator along with the permissions above.

Over years of answering support tickets we saw the same problem again and again: most servers have channel and category permission overrides that hide channels from the bot, so tickets would not open, transcripts and logs never arrived, and the dashboard reported channels the bot could not use.

Fixing that meant changing permissions in Discord channel by channel. Administrator lets the bot see and post in the channels and categories you choose without any of that.

  • The bot only uses it for tickets. It never bans, kicks, or times out members, and never changes your server's settings.
  • Your bot token is encrypted before it is stored, and only the bot owner can manage the bot in the dashboard.
  • You can untick Administrator on Discord's authorize screen. The other permissions in the list still let every ticket feature work, but then make sure the bot can see the channels and categories you pick.
  • Bots invited before October 2026 keep the permissions they were given. To add Administrator, invite the bot again with Invite to a server in the dashboard; it keeps its settings.
  • Administrator does not change the role order. Discord still only lets a bot give roles that sit below its own role (see below).

Invite the bot only from the dashboard: with Add bot in the guided setup, or with Invite to a server. Adding it any other way is not supported, whether with an invite link you build in the Developer Portal or with Discord's Add App button on the bot's profile.

The dashboard invite checks that you manage the server, asks for exactly the permissions and scopes TicketCord needs, and waits until the bot has joined. Other invites skip all of that and usually miss permissions or the applications.commands scope, which shows up later as tickets that will not open, transcripts that never arrive, or commands that do not appear.

If the bot was added another way, kick it and invite it again from the dashboard; the token stays valid and the server keeps its settings.

After the invite

  • Discord places the bot's role at the bottom of the role list. Drag it above your staff roles in Server Settings → Roles so it can manage permissions for them.
  • The bot can only give roles that sit below its own role, such as the role members get while a ticket is open (Opening tickets → Ticket options → Role while open). When a role is out of its reach, the dashboard says so under the role picker; click Show me how to see your server's role list with the bot's role dragged into place, then Reload from Discord.
  • Finish the setup on your server: pick the staff roles, ticket categories, and channels, or let Create them for me create them (/setup in Discord creates the same set). See Configuration.
  • Run /diagnose to confirm the bot can see every channel and category it will use.

Troubleshooting

SymptomCauseFix
The token check says "Turn on Server Members Intent and Message Content Intent" (Add a bot) or "Discord would not turn on the privileged intents this bot needs." (guided setup)Server Members Intent or Message Content Intent is offEnable both on the Bot tab, then check the token again
The invite fails with "Integration requires code grant"Requires OAuth2 Code Grant is on for your applicationOpen the Bot tab in the Developer Portal, switch Requires OAuth2 Code Grant off, save, and invite the bot again with Invite to a server
"Private application cannot have a default authorization link" when you turn off Public BotThe Installation tab still has a default install linkSet Install Link to None on the Installation tab, save, then switch Public Bot off
Bot shows offline after you reset the tokenThe old token no longer worksOpen the bot's Bot profile page in the dashboard, click Update token, paste the new token, click Continue, then Save new token. The bot restarts on its own
Bot is online but slash commands do not appearThe invite lacked the applications.commands scopeKick the bot and invite it again with Invite to a server, then reload Discord (Ctrl+R / Cmd+R)
Replies arrive without a TC code footerSomething else is running the same tokenStop the other program, reset the token, and update it on the bot's Bot profile page
"Bot Cannot Access This Server" (TC002)The bot's role lost View Channel at the server levelRestore the permission on the bot's role under Server Settings → Roles
"TicketCord isn't a member of this server" (TC004)The bot was kickedInvite it again with Invite to a server

Common questions

Why does Discord say "Integration requires code grant" when I invite my bot? The application has Requires OAuth2 Code Grant switched on in the Discord Developer Portal. TicketCord invites the bot with a standard bot invite, which Discord rejects while that setting is on. Open the Bot tab, switch Requires OAuth2 Code Grant off, save, and invite the bot again from the dashboard.

Can I use an existing bot application? Yes. Paste its token. Make sure Public Bot is off (TicketCord turns on the privileged intents when it checks the token), and invite it from the dashboard so the permissions are right.

Do I need to keep anything running on my computer? No. TicketCord hosts and runs the bot for you. You only supply the token.

Can I add the bot with my own invite link or Discord's Add App button? No. Invite it only from the dashboard, with Invite to a server (or Add bot in the guided setup). Invites made any other way are not supported: they skip the dashboard's checks and usually leave the bot without the permissions or the applications.commands scope it needs. If you already added it another way, kick it and invite it again from the dashboard.

Can one bot be in several servers? Yes. Invite it from the dashboard to each server and configure each server separately. The number of bots you can create depends on your plan: 1 on Free, 3 on Basic and Pro, 6 on Enterprise.

I changed the bot's name and avatar in the Developer Portal. When does the dashboard update? Automatically. The bot picks up the new name and avatar from Discord while it is online, and checks again each time it starts. If the dashboard still shows the old values, press Restart on the bot's Bot profile page.

Does TicketCord store my token? Yes, encrypted, so that it can run the bot. Resetting the token in the Developer Portal invalidates the stored copy; paste the new one with Update token on the bot's Bot profile page.

Why does the invite ask for Manage Roles and Mention Everyone? Manage Roles lets the bot set per-ticket permission overwrites so only the creator and staff can see a ticket. Mention Everyone lets it ping staff roles when a ticket opens even when those roles are not otherwise mentionable.

Last updated on

On this page