Modbot Docs
Discord

Permission watch

Get told when a Discord role or member, a bot among them, gains Administrator or another dangerous permission. Optionally have Modbot take the permission away.

A role that quietly gains Administrator, or a bot that joins with a role that has it, can take a server over. Permission watch notices when that happens and tells your staff. It can also undo it, but only if you turn that on.

The watch is always running once the bot is set up (Setting up the bot). Nothing is removed unless you ask for it.

What is watched

Permission
Administrator
Manage Server
Manage Roles
Manage Channels
Manage Webhooks
Ban Members
Kick Members
Mention Everyone
Manage Messages

Two things count as a gain:

  • A role gains one. A role that already existed and now has a permission from the list it did not have before, or a role that was made with one.
  • A member is given a role that has one. This includes a bot that joins with its own role.

Modbot tells you the first time a role has the permission, not again on every later check.

Where you are told

Every gain is recorded as a fact, Discord role gained a dangerous permission or Discord member given a dangerous permission. You see it in the audit log, and you can send it to a channel from Settings → Discord → Channels, like any other event (Event channels).

To get a message straight in your staff room as well, open Settings → Discord and find the Permission watch card. You need the Change settings permission.

SettingWhat it does
Staff channelWhere Modbot posts a card for each gain. The bot needs to see the channel, send messages and embed links. Leave it empty to use the fact log and channel routes only.
Remove automaticallyOff by default. Also takes the permission away.

The card names the role or member, the permissions, and what happened: Permission removed, Left as it was, or Could not remove with the reason.

Remove automatically

When it is on:

  • A role that gained a permission loses exactly the permissions it gained.
  • A member who was given a role that has one loses that role.
  • For a bot's own role (the one Discord made for it when it joined), Discord does not let the role be taken off the bot, so the permissions are taken off the role instead.

Modbot never removes permissions from its own role. If someone gives Modbot's role a permission from the list, staff are told and the card says Left as it was: Modbot's own role. Taking it away would stop Modbot from doing its job.

@everyone is treated like any other role: if it gains one of the listed permissions, only those permissions are taken off it.

The server owner never loses anything: they are told about, and the card says the member is the owner. If Discord does not allow Modbot to do it, for instance because the role sits above Modbot's own in Server Settings → Roles, nothing else is tried and the card says so.

What it leaves alone

  • Roles Modbot gave in the last few minutes, such as the ones from the join gate, account linking and roles from lists, and Modbot's own account.
  • The first time Modbot reads a server: everything that is already there stays as it is.
  • Members Modbot has no stored roles for yet. They are picked up the next time their roles are stored, and a person given a dangerous role before then is not reported.
  • A bot that joins with a role of its own is reported twice, once as a new role and once as a member given a role.

Modbot is not endorsed by or affiliated with VRChat Inc. or Discord Inc. VRChat is a trademark of VRChat Inc. Discord is a trademark of Discord Inc. SteamVR is a trademark of Valve Corporation. Windows is a trademark of Microsoft Corporation. Docker is a trademark of Docker, Inc. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Railway is a trademark of Railway Corp. Other names are trademarks of their respective owners; see Legal. Modbot and its logo are trademarks of the Modbot project. Open source under AGPL-3.0.

On this page