Permissions & intents
By the end of this page, you’ll know exactly what each permission Tickets asks for is actually used for.
Tickets doesn’t need Administrator - it never touches roles, channel overwrites, bans, or server settings. It only creates/manages ticket threads and sends messages/embeds. The invite link on the previous page already requests exactly this set - nothing more.
Bot permissions
Section titled “Bot permissions”The invite link’s permission integer (360777337856) breaks down to:
- View Channels
- Send Messages / Send Messages in Threads
- Create Private Threads
- Manage Threads - archiving/locking closed tickets; adding/removing thread members for
/close,/claim,/remove-user - Read Message History - transcript generation reads a thread’s full history at close time
- Embed Links - every reply/notification is an embed
Gateway intents
Section titled “Gateway intents”In the Discord Developer Portal’s Bot page, also enable these Privileged Gateway Intents. The bot requests exactly Guilds, GuildMembers, GuildMessages, and MessageContent - of those, GuildMembers and MessageContent are privileged and need an explicit toggle:
- Server Members Intent - thread-membership checks, and the auto-close-on-opener-leave behavior (see Claiming, closing & auto-close)
- Message Content Intent - transcript caching needs the actual message text
Presence, voice, reaction, and moderation intents aren’t requested - nothing in Tickets uses them.
Continue to The dashboard, first login.