WARDEN Docs | Setup and Discord Server Protection
Back to Home

How WARDEN Works

Use this as the owner-facing guide for each dashboard area: what it protects, what happens when it is enabled, and a safe starting configuration.

Anti-Nuke Thresholds

Protects: Stops rapid destructive admin actions such as role deletes, channel deletes, bans, kicks, webhooks, emoji, stickers, invites, and threads.

When on: When a user crosses a threshold inside the configured time window, WARDEN applies the selected punishment and logs the exact reason breakdown.

Start with: Start with limits of 3 actions per 10 seconds for roles/channels/assets, and keep nuke score threshold around 8.

Anti-Raid

Protects: Detects sudden join spikes and waves of suspicious new accounts.

When on: If joins exceed your limit inside the raid window, the bot can quarantine, timeout, kick, ban, or trigger lockdown.

Start with: Use 10 joins per 10 seconds with quarantine for normal servers; use lockdown only for high-risk communities.

Quarantine

Protects: Contains suspicious users without immediately banning them.

When on: The bot removes dangerous roles, applies the quarantine role, stores restorable role snapshots, and lets staff release the member later.

Start with: Keep quarantine enabled with channel restrictions on and review the Quarantine panel daily.

Heat / Anti-Spam

Protects: Stops repeated spam, mention spam, and coordinated message abuse.

When on: Messages increase a user heat score; crossing the limit applies the configured action and may trigger panic handling.

Start with: Use timeout as the first action, then tune the heat limit upward if normal chat is very active.

Join Gate

Protects: Flags new, no-avatar, invite-name, suspicious-name, bot, and shared-threat accounts at join time.

When on: Each signal contributes to a risk score; users over your threshold get the selected action automatically.

Start with: Use a 70 risk threshold, quarantine action, no-avatar checks on, and invite-name checks on.

Verification

Protects: Adds a soft checkpoint before suspicious or all new members receive normal access.

When on: The bot starts verification based on your mode and target setting, then times out stale verification sessions.

Start with: Use suspicious-only verification first; switch to all-members during raids or public launches.

Backup / Restore

Protects: Lets owners recover missing roles and channels after destructive events.

When on: Backups are scheduled and manual; restore preview shows what will be added before the real restore applies.

Start with: Keep scheduled backups on and create a manual backup after major server layout changes.

Panic Mode

Protects: Seals the server when a severe raid or multi-vector attack is detected.

When on: Lockdown restricts public changes and can auto-recover roles/channels based on current settings.

Start with: Enable auto-recovery and only use manual lockdown when you are sure staff credentials are compromised.

AutoMod

Protects: Installs Discord-native rules for invite links, scams, phishing, token grabbers, IP loggers, raid threats, spam, mentions, and profile ads.

When on: The dashboard syncs the managed rule pack per guild and shows whether every rule is active, disabled, or missing.

Start with: Enable the full managed pack, then remove only rules that conflict with your community format.

Whitelist / Watchlist

Protects: Separates trusted operators from suspicious accounts without hiding either from staff.

When on: Whitelisted users bypass protection checks; watchlisted users stay visible for future review and join-risk context.

Start with: Whitelist only permanent senior staff. Use watchlist for investigation, not punishment.

Dashboard Access / RBAC

Protects: Avoids one-owner bottlenecks while keeping write access controlled.

When on: Owners can grant read-only or write dashboard access to trusted Discord user IDs.

Start with: Give read access broadly to security staff and write access only to two or three trusted admins.

Settings Templates

Protects: Keeps multi-server deployments consistent.

When on: Owners can save a known-good settings profile and apply it to another server they own.

Start with: Create one baseline template for public servers and one stricter template for tournament or launch days.