Permissions and role hierarchy

The 12 audited permissions

• View Channels
• Read Message History
• Send Messages
• Send Embeds
• Manage Messages
• React
• Timeout Members
• Kick Members
• Ban Members
• Assign Roles
• Manage Roles
• Manage Nicknames

Role hierarchy

Move the Stoatmod role above every ordinary member it needs to moderate and every role it needs to assign. Stoat rejects role assignment, nickname restoration, timeouts, kicks and bans when the acting bot is not high enough in the hierarchy.

Important: A success-looking audit record is not proof that the member or role changed. Verify the resulting server state after setup and after any permission change.

Log-channel access

• The bot must be able to view the selected channel.
• It must be able to send messages and embeds there.
• Category-specific channel permissions can override a broader server role.
• A working command in one channel does not prove access in another.

Audit and recovery

1. 01

   Run setup

   Collect the current permission and hierarchy findings.

   ~setup
2. 02

   Fix from the top down

   Correct the bot role position before troubleshooting individual actions.

3. 03

   Recheck the target

   Confirm the member, role and channel are inside the bot's effective access.

4. 04

   Repeat one controlled action

   Verify both the response and the real outcome.