Permissions and roles

1 min read

When invited, BitGuard only asks for the permissions its modules need. The bot does not need Administrator.

Requested permissions

  • View channels, send messages, read historyThe basis for every module
  • Manage messagesAutoMod deletes violations
  • Kick, ban and time out membersModeration, anti-raid, anti-nuke
  • Manage rolesAuto roles, reaction roles, level roles, verification
  • Manage channelsTickets, temporary voice channels, stats channels
  • View audit logAnti-nuke uses it to see who deleted something
  • Manage webhooksSocial alerts with a custom name and avatar (Premium)
  • Manage Server (optional)Only for the invite tracker, so BitGuard can read the invite links. The bot does not ask for it when invited, grant it yourself if you need it.
  • Move members, manage nicknamesTemp voice and name rules

Role order

The BitGuard role must be above every role the bot should hand out and above the members it should moderate. Your admin roles may sit above it.

  1. Owner / adminsat the top
  2. BitGuardbelow them
  3. Member and community roleseverything BitGuard should hand out or moderate
BitGuard does not hand out dangerous roles

Roles with permissions like Administrator, Manage Server or Ban cannot be used as auto roles, reaction roles or level rewards.

Who may do what in the bot

In the dashboard under Permissions, you decide which roles may use the moderation commands, separately for mute, warn, kick and ban. The server owner may always do everything.

There you also pick an AutoMod admin who may change the rules, a level admin role for /xp and an economy admin role for /coins.

Anyone with Manage Server on the server can open the dashboard. BitGuard checks this again on every change.

Still have questions?

The BitGuard team helps you on the support server.

Support server