Getting started

Permissions

Mira needs specific Discord permissions to work. Granting them all on invite is recommended — denying some features will silently break.

Permission integer

On invite, Mira asks for 1099780451462. This is the bitmask that Discord uses to encode the permission set below.

What each permission is for

Permission	Used for
`Manage Server`	Reading server-level settings, audit log access
`Manage Channels`	Creating ticket channels, configuring slowmode
`Manage Roles`	Auto-roles, level rewards, verification grant, ticket overwrites
`Manage Webhooks`	Logging messages with author preserved
`View Channels`	Reading messages for auto-mod and logging
`Send Messages`	All output
`Send Messages in Threads`	Suggestion auto-threads, etc
`Embed Links`	Rich embed output (welcome, audit, mod log)
`Attach Files`	Ticket transcripts
`Read Message History`	Purge, transcripts, audit context
`Use External Emojis`	Custom emoji in embeds
`Add Reactions`	Reaction roles, poll buttons
`Mention @everyone`	Only when you explicitly configure a ping role
`Kick Members`	Kick command, anti-nuke kick punishment
`Ban Members`	Ban command, anti-nuke ban punishment
`Moderate Members`	Timeout-based mute

Role hierarchy

Discord enforces this: a bot can only manage roles below its own role. Move Mira's role above:

Any role granted by auto-roles or verification
Any role granted by level rewards
Any role you want Mira to remove on a kick / ban target

Privileged intents

Mira uses three privileged intents that you cannot configure — they're set on our side at the Discord developer portal:

Server Members — required for welcome, leveling, role management
Message Content — required for auto-mod, autoresponder
Presence — required for the "online members" count on the dashboard

Dashboard access

The dashboard uses Discord OAuth and only shows servers where you have Manage Server. There is no role-based dashboard access today — if you can manage the server, you can manage Mira's settings for it.