Integrity

Integrity keeps a trusted picture of your server's permission structure and defends it. It takes a snapshot of who holds which roles, what each role can do, and which webhooks exist. Then it watches for changes that quietly hand someone more power than they should have. When a dangerous grant slips through, Integrity reverts it automatically and logs what happened.

What counts as escalation

A role suddenly gaining Administrator or Manage Server, a member being handed a role well above their station, a new webhook appearing in a sensitive channel, or permission overwrites that open a locked channel. These are the moves an attacker or a rogue integration makes right before real damage.

Commands

,integrity on|off                enable or disable Integrity
,integrity channel <#channel>    where reverts and alerts are logged
,integrity whitelist <@role>     mark a role or member as an allowed source of changes
,integrity resnapshot            re-capture the current state as the new trusted baseline

Whitelist the people and bots that are supposed to change permissions: your owner, a role manager, a trusted integration, so their legitimate work isn't rolled back.

Setup

Get your roles and webhooks into the shape you want first, then run ,integrity resnapshot so the baseline reflects a clean state. Any time you intentionally restructure permissions, resnapshot again so Integrity doesn't revert your own work.

Review the trusted snapshot, whitelist, and revert history on the Integrity dashboard page.