Getting started

Security Bot Setup Guide

Protect a Discord server in five minutes: invite Security Bot, fix role order, review anti-nuke limits, turn on verification, set logs, whitelist admins.

10 steps

Set up Security Bot step by step

Steps 1 to 7 and step 10 are free. Steps 8 and 9 cover Premium.

  1. Step 1: Invite Security Bot

    Use the official invite from securitybot.gg. Security Bot requires the Administrator permission. Without it, anti-nuke ignores events and the dashboard cannot save settings. Only invite from this site or the documentation to avoid lookalike bots.

  2. Step 2: Move the bot's role to the top

    Open Server Settings, Roles, and drag the Security Bot role above every staff role. The bot can only act on members below it. Members whose highest role is above it are exempt from anti-nuke. Only the server owner and Administrators ranked above the bot can manage its settings. With the bot at the top, that is usually just the owner.

  3. Step 3: Log in to the dashboard

    Go to securitybot.gg, press Login, and authorize Discord with the identify and guilds scopes. Pick your server. Free servers can also change settings with slash commands. On Premium, settings commands reply with a dashboard link, so settings are changed on the dashboard.

  4. Step 4: Review anti-nuke limits

    Seven free triggers are on by default: banning, kicking, creating and deleting channels, creating and deleting roles, and adding bots.

    Premium also starts with Anti Mention Spam on (limit 8) and Anti-Spam on (20 messages in 8 seconds, auto clear and auto lock). That lock stays until someone runs /unlock unless you set a lock duration.

    Pruning members, Admin Role Assign (giving a role that holds a dangerous permission), Role Permission Change (editing such a role's permissions), and the invite-link filter are off until you turn them on.

    Default limits are 5 bans, 5 kicks, 3 channel or role deletions, and 8 channel or role creations. Counters reset every 10 minutes, and the punishment fires when a member reaches the limit. Choose Kick, Ban, or Clear Roles per trigger. Kick is the default, except Ban for pruning.

    Command: /settings category:Anti Nuke

  5. Step 5: Turn on verification

    Enable verification and choose a type. Adaptive is the recommended pick: it lets low-risk members straight in and sends the rest to Captcha Code or the Web Check. The others are Web Check (a 5-second browser check, nothing to solve), Captcha Code (an image the member answers with /verify), and One-Click. For invite-only servers, pick Server Passcode (a code you share) or Allowlist (only listed user IDs stay).

    When the bot creates the Unverified role and the verification channel, it adds a channel overwrite that hides every other existing channel (text, voice, announcement, forum, stage, and media) from that role. Role order does not decide channel access.

    For channels you create later, run /verification update_role or add the same deny yourself. Make sure no other role new members get (for example from an auto-role bot) is allowed View Channel on those channels. Keep Security Bot's role above Unverified so it can remove it.

    Command: /verification enable

  6. Step 6: Set log channels

    On the Logging page, assign a moderation log and a security log channel. The moderation log records the bot's moderation commands except /clear and /raid ban, plus anti-raid timeouts and channel locks. The security log records anti-nuke warnings, anti-nuke and Beast Mode punishments, anti-raid locks, web check denials, possible alt accounts, and raids that Adaptive Verification detects. Premium adds audit and AutoMod log channels.

  7. Step 7: Whitelist your admin role

    Exempt your admin role from the actions it performs in bulk, per action rather than globally, so anti-nuke does not fire on routine cleanup. Each whitelist command needs a category, such as Roles: Channel-Delete.

    Command: /whitelist add_role role:@Admin category:Roles: Channel-Delete

  8. Step 8: Optional: add Premium

    Premium costs from $4.99 per month for one server. It adds score-based anti-raid with channel lockdown, anti-spam, AutoMod presets with link filtering, Recovery (automatic server backups and restore, once you turn it on), 10 more anti-nuke triggers, and /banid and /raid ban.

    It runs on a separate bot. After checkout, assign a slot to your server on the dashboard, then add the Premium Bot. That bot leaves servers without a slot. Settings from the free bot do not carry over, so set them up again on the dashboard.

    Add the Premium Bot after the slot is assigned.

  9. Step 9: Enable AutoMod presets (Premium)

    On Premium, open the AutoMod page and turn on Block Mention Spam, Block Suspected Spam Content, and Block Commonly Flagged Words. Security Bot creates the matching Discord AutoMod rules, which use your server's AutoMod rule slots. Threat Link Guard and Mature Link Guard are filters the bot runs itself and use no Discord rule slot.

  10. Step 10: Test it

    Join with an alt account to see verification. Mute the alt for a minute to see the moderation log. Open the dashboard's Beast Mode simulator to see how Beast Mode reacts to an example attack. Adjust anything that fires on normal staff work.

Suggested values

Suggested settings by server size

Starting values to enter yourself; the bot has no built-in presets. Anti-nuke counters are per member and reset every 10 minutes. Adjust after a week of reading the security log.

Server sizeAnti-nukeAnti-raidVerification
Under 1,000 membersBan and kick limit 2 per 10 minutes, Clear RolesPremium only: keep the default score limit of 200; if you lower it, use Mute instead of BanAdaptive on Relaxed, or One-Click
1,000 to 20,000 membersBan limit 3, kick limit 3 per 10 minutes, Clear RolesPremium only: score limit 200 (the default) or higher if normal join waves come close, lockdown onAdaptive on Balanced
20,000+ members or public communitiesBan limit 3 per 10 minutes, Ban punishment on channel and role deletePremium only: raise the score limit above 200 in line with your normal join volume, lockdown onAdaptive on Strict, or Web Check with VPN and alt blocking; set Beast Mode points

Anti-raid limits: with the default scores, every join that is not bypassed adds at least 2 points within the 20-minute window. When the limit is reached, every unpunished join in that window gets the punishment, which is Ban by default. At a limit of 15, eight ordinary joins in 20 minutes would set off the raid response and ban all eight. If you set a low limit, choose Mute.

Questions

Setup FAQ

Why does Security Bot ask for Administrator?

Administrator is required. Without it, anti-nuke ignores the events it watches and the dashboard refuses to save settings. With it, the bot can kick, ban, or clear the roles of accounts below its role, create the Unverified role and verification channel, and lock channels.

Do I need to use slash commands?

No. Every setting is on the dashboard at securitybot.gg. Free servers can also change anti-nuke, whitelist, verification, log, and command permission settings with slash commands. On Premium, settings commands reply with a dashboard link instead. Moderation commands such as /ban and /lock run in Discord on every plan.

How long does setup take?

About five minutes for the free protections: invite, role order, anti-nuke review, verification, logs, and whitelist.

What is free and what is Premium?

Free: anti-nuke with 10 punishable triggers plus an invite-link filter, verification (Adaptive, Web Check with VPN and alt blocking, Captcha Code, One-Click, Server Passcode, Allowlist), 11 moderation commands, Beast Mode, whitelists, and moderation and security log channels. Premium adds score-based anti-raid, anti-spam, AutoMod presets with link filtering, Recovery with server backups and restore, 10 more anti-nuke triggers including webhook creation, /banid and /raid ban, and audit and AutoMod log channels. It runs on the separate Premium Bot.

What should I do first if I am being attacked right now?

Invite the bot, move its role above your staff roles, and run /lockall to lock every regular text channel. Pause invites under Server Settings, Invites, then enable verification. The seven default anti-nuke triggers work as soon as the bot has Administrator.