πŸ³οΈβ€πŸŒˆ
Pride Doesn't End Here

Only what's needed, nothing more.

Kuma requests the minimum permissions to function. Required permissions power core features; optional ones unlock specific commands you may not need.

8
required
4
optional
12
total

Server permissions

Required permissions
View ChannelsRequired

So commands and messages can be read.

Send MessagesRequired

To respond to commands and post logs.

Manage MessagesRequired

For AutoMod removals and !purge.

Embed LinksRequired

For richly formatted replies and logs.

Timeout MembersRequired

Required for !mute, the auto-mute threshold, and the raid waitlist (holding new joiners during a raid).

Manage RolesRequired

For !temprole, !levelroles, !reactionrole, !autorole, and !verify.

Add ReactionsRequired

For !poll, reaction roles, and verification.

Manage WebhooksRequired

For !webhook and external integrations.

Optional permissions
Kick MembersOptional

Required for !kick.

Ban MembersOptional

Required for !ban, !unban, !softban, and !raid cleanup.

Manage ChannelsOptional

Required for !lock, !unlock, and !panic.

MasqueradeOptional

Stoat only. Lets bridged messages and tuppers post under the original name and avatar. Without it they still send, just under Kuma's name with the author prefixed. Discord and Fluxer do the same thing through Manage Webhooks.

Please give Kuma the permissions it needs. After inviting the bot, assign its role the permissions for the features you want to use in your server settings. Missing a permission later? Just update the bot's role, no re-invite needed.