Command Reference
Complete documentation of all AiGuild bot commands. Search, explore and integrate quickly.
Discord Permissions Guide
Discord permissions are powerful but complex. Role hierarchy, channel vs server permissions, edge cases — many admins get lost and end up giving everyone Administrator or checking every box. This guide demystifies the system.
01How Discord permissions work
Discord uses a layered system: server permissions (at the role level) and channel permissions (which can override role permissions). A user accumulates all permissions from all their roles. The golden rule: one enabled permission on any role wins, unless the channel explicitly blocks it.
02Role hierarchy
The order of roles in Discord's list determines who can moderate whom. A moderator can't sanction someone with a higher role than their own. The AiGuild bot itself must have a role higher than the roles it creates to manage them. Always place the bot's role at the top of the hierarchy.
03Critical permissions to configure
@everyone: disable Send Messages in announcement channels, disable Mention @everyone. Moderators: enable Manage Messages, Kick Members, Mute in voice. Members: enable Send Messages, Add Reactions, Connect to voice channels. Only give Administrator to trusted admins — this permission bypasses everything.
04Channel vs server permissions
Channel permissions take priority over server permissions for that specific channel. Example: even if @everyone can read messages, a private channel can block @everyone and only allow the @VIP role. This is how staff-only categories work.
05Automate with AiGuild
AiGuild configures all permissions automatically during generation. Each generated role receives precise permissions tailored to the server type. Hierarchy is respected, sensitive channels are protected, and the bot automatically places itself in the correct position.