Roo Protector Documentation

First-time setup

Invite Roo Protector with the permissions required by the modules you plan to use. Administrator permission is not required.
Run /setup to create the log category and webhook destinations. The bot needs Manage Channels; webhook delivery additionally needs Manage Webhooks.
Run /verification-setup to create the Verified and Unverified roles, the verification channel, and the button/modal panel. Configure the rest of the server's channel visibility so only Verified members can access member channels.
Open the web dashboard to configure protection thresholds, trusted roles/users, log destinations, and module toggles.

Verification

Members click the button in the server's verification channel and answer the configured modal questions. Answers are validated by the bot and are not stored. On success, Verified is added and Unverified is removed. The bot must have Manage Roles, and both roles must be below the bot's highest role. Review other role/member overwrites as well: a separate role can still grant access even when Unverified has a category deny.

Cross-server ban intelligence

Apply in the server dashboard under Sharing Network.
A platform administrator reviews the application at /platform/sharing. Approval does not enable sharing.
The server owner or a Manage Server administrator runs /sharing enable.
Run /sharing sync to publish the current ban list. New bans publish while sharing remains enabled; unbans retract active records.

Use /sharing status, /sharing profile user, /sharing update user reason, /sharing disable, and /sharing remove to manage the integration. Shared matches are review signals only. Historical reasons and occurrence times are only shown when Discord has an exact stored record for them.

Moderation

Use /ban, /kick, /timeout, /warn, and /purge. Actions are recorded with a unique case ID. Use /cases to search recent cases and /case view or /case edit to review or correct a reason. Roo Protector attempts to DM the affected user with the action, case ID, and reason; Discord privacy settings may prevent delivery.

Security notes

Anti-nuke and anti-raid defaults are alert-only. Review thresholds and trusted users before enabling automatic responses. Keep the bot role below the server owner and trusted administrator roles, but above roles the bot must assign or manage. Never share the bot token, OAuth client secret, database password, or session secret.

Read the Privacy & Data policy.