What the bot asks Discord for
The invite requests only what the shipped modules actually need — it is not a blanket Administrator grant.Privileged intents
Two intents must be enabled in the Discord Developer Portal or parts of the bot silently do nothing:Server Members
Onboarding, invite tracking, autoroles, birthdays, and anything that reacts to a member
joining or leaving.
Message Content
Prefix commands, anti-phishing scanning, sticky messages, leveling, and AFK.
Role setup
Role panels, autoroles, and mass role all move member roles, which means V.O.I.D’s own role needs to sit above any role it’s asked to manage in your server’s role list. Discord refuses role changes from a lower role regardless of what permissions the bot has — this is the single most common reason a role-related command silently does nothing.Who can run what
Every command declares a policy, and it is checked when the command runs — not only when a panel is drawn. Reopening a panel with a stale button will not bypass it.
Set your privileged roles with
=setadmin and =setstaff. Until you do, only Manage Server and
Administrator count.
The dashboard is read-only for settings. Changes happen in Discord so that permission checks
and audit logging live in one place — there is no path where a web session can change
something Discord would have refused.