Inviting the bot
The invite uses thebot and applications.commands scopes — applications.commands is what
lets Discord register the bot’s slash commands in your server.
What the bot asks Discord for
Ticket Bot is centrally hosted, so you won’t generate this invite yourself — but knowing what
it asks for explains why some actions (renaming a pinned ticket, adding a participant) need
specific permissions in place.
Privileged intents
Two intents are enabled by the bot and must be allowed in its Discord application:Server Members
Drives close-on-leave (
;ticketcloseonleave) and resolving guild members for DMs (key
delivery, AIO order notices).Message Content
Required for the bot’s prefix commands (
;confirm, ;pinticket, ;unpinticket,
;autocloseticket, ;ticketcloseonleave) to be parsed at all — without it, Discord never
delivers message text to the bot.Who can run what
Ticket Bot’s authority system is independent of Discord’s native permission bits, and it is checked when a command runs, not just when a panel is drawn — reopening a stale panel does not bypass it.Staff tiers
Assigned with/staffrole set, which maps a Discord role to one of these tiers. The server
owner and the bot’s configured owner(s) always hold full (Owner) authority implicitly,
regardless of role mappings — you can never lock yourself out.
Staff → Manager → Admin → Owner is a genuine seniority ladder — each tier includes everything
below it. Reseller, Sales, and Support below are not part of that ladder.Peer specialist tiers
Reseller, Sales, and Support are independent specialty tiers, not rungs on the ladder
above — holding one grants nothing from another, even though their internal numbering might
suggest otherwise.
Capabilities
Some commands check a specific capability rather than a tier directly. EveryStaff+ tier holds
the capabilities below; Support and Sales hold a subset relevant to their specialty (see
above).
See each command’s own page in Commands for exactly which tier or
capability it checks.