Actor permissions
Each command documents its requirement: for example,.vanity requires Administrator, .alias requires Manage Server, .afklist requires Manage Messages, and .privatevc lobby requires Manage Channels. Checks run in the server and can differ by subcommand.
Actor-permission examples
Bot permissions and hierarchy
In addition to actor authorization, Headless needs the native permissions required for the action. Review Manage Channels for channel changes; Manage Roles and role hierarchy for roles; and Move Members for relevant voice operations. An authorized command can still fail if Discord blocks the bot.Channel changes
Virtual permissions
Fake Permissions is a separate, limited system. It does not edit Discord permissions; it provides virtual context only to Headless checks. Only the server owner or Headless owner can manage it, and the virtualadministrator key substantially broadens access.
Inspect virtual permissions
Steps
1
Read the command requirement
Open the feature guide and check both the actor’s Discord permission and the bot’s permissions.
2
Check role and channel
Review the bot role hierarchy and overwrites on the target channel.
3
Test with minimum scope
Try a test channel/member before granting broader access.
Access, configuration, and support
1. Sign in with Discord
OAuth2 identifies the operator and shows servers their account is authorized to manage. Membership alone is not enough; server access is checked again for sensitive actions.
2. Per-server configuration
Modules keep their own settings. Channels, roles, and other values are validated for the selected server, and required permissions can differ by feature.
3. Maintenance
The server view exposes health, recent activity, and last-sync status to help identify missing permissions or settings that have not synchronized yet.
4. Safe changes
The API checks access again before accepting changes; some actions provide a preview before confirmation. Backups are not a setting in the public Dashboard and should not be assumed available from this guide.
5. Support
Contact support when an issue requires checking bot permissions, an integration, or an incident. Never send tokens, passwords, or webhook secrets.