Reverse Security
Log in with Discord

Getting started

Invite, role position, /autoconfig and /diagnostic.

  1. Invite the bot with the dashboard or website button. It requests the specific permissions its modules need — not Administrator.
  2. In Server Settings → Roles, move the bot's role above every role you want it to be able to act on. Discord never lets a bot manage, kick, ban or time out members whose highest role is equal to or above its own, and nobody can act on the server owner.
  3. Run /autoconfig and choose a level: light, standard or strict.
  4. Run /diagnostic. Every module shows OK, degraded or out of service with the exact reason (missing permission, role hierarchy, provider not configured, stale threat feeds…).
  5. Open the dashboard to fine-tune thresholds, channels and roles.

How dashboard changes are applied

The dashboard never touches Discord with your browser credentials. A change becomes a request; the bot's worker re-checks your current Discord permissions and role hierarchy immediately before applying it, then reports the real outcome (applied, partially applied, rejected with the reason, failed, or expired). Every change is recorded in the audit history.