Permissions
Discord permissions and role hierarchy needed by Aripa commands.
Aripa checks the invoking user's permissions before running protected commands. Discord also checks the bot's own permissions when Aripa performs the action. Both must pass.
User Permissions
| Command | Required user permission |
|---|---|
-logs | ManageGuild |
-banmessage | ManageGuild |
-muterole | ManageGuild |
-tag add, -tag edit, -tag remove | ManageMessages |
-warn | ModerateMembers |
-mute | ModerateMembers |
-unmute | ModerateMembers |
-kick | KickMembers |
-ban | BanMembers |
-unban | BanMembers |
-cleanban | BanMembers |
-clean user | ManageMessages |
-role add, -role remove | ManageRoles |
General utility commands such as -ping, -help, -info, -server, and
-avatar do not require special Discord permissions.
Bot Permissions
Give the bot the Discord permissions needed for the actions you expect it to perform. For a moderation-focused server, that commonly includes:
- View Channels
- Send Messages
- Read Message History
- Manage Messages
- Moderate Members
- Kick Members
- Ban Members
- Manage Roles
Role Hierarchy
Discord prevents bots from managing members or roles above their highest role. If a command fails even though permissions look correct, check:
- The bot role is above the target member's highest role.
- The bot role is above any role it needs to add or remove.
- The invoking user's role is high enough for the same action.
- The target channel allows the bot to send messages.
Mute Roles
Configured mute roles must be manageable and must not grant Discord
permissions. If -muterole @Muted fails, check the mute role's position and
permissions.