To set up Wick, invite it from its official site, then go to Server Settings > Roles and drag the Wick role to the top so it sits above every role it might need to act on. Then run Wick's setup or dashboard wizard, set your anti-nuke limits, and whitelist trusted admins and bots before you tighten anything, so your own staff don't get punished. Turn on verification last.
Checked on each bot's own site or docs on 3 November 2026. We make PeakBot. Nobody paid to be in this post.
Wick is a security bot. It offers anti-nuke and heat-based automod, and puts anti-raid, extended anti-nuke and backups on Premium. Most setup problems with Wick come from Discord's role rules, not from Wick. So this guide covers the Discord side in detail and tells you where each Wick setting lives. Wick changes its menus and command names between versions, so check exact command names against the docs on wickbot.com as you go.
Before you start
- You need to be the server owner or have Administrator.
- Use desktop or a browser. Inviting a bot and reordering roles are easiest there.
- Write down every account and bot that legitimately does bulk actions: co-owners, head mods, ticket bots that create channels, auto-role bots that hand out roles, and bots that create temporary voice channels. You will whitelist these in step 5.
Step 1: Invite Wick
- Open wickbot.com and use the invite button there. Bot listing sites also list bots with similar names (Wicks, Wickie), so use the official site.
- Pick your server and keep the permissions Wick asks for. A security bot has to undo damage anywhere in the server. Discord's docs say Administrator "allows all permissions and bypasses channel permission overwrites" (Discord permissions docs). That is why security bots usually ask for it.
- Click Authorize and finish the captcha.
When a bot joins with permissions, Discord creates a role with the bot's name. If you untick every permission, that role may not appear, and that causes most "Wick has no role" problems.
Step 2: Move the Wick role to the top
Discord's rules here are strict. A bot "can only kick, ban, and edit nicknames for users whose highest role is lower than the bot's highest role," and it can only edit roles below its own highest role (Discord permissions docs). If Wick sits below your mod role, it can't stop a compromised mod.
- Open Server Settings > Roles.
- On desktop, drag the Wick role to the very top of the list, above your admin and moderator roles.
- Click Save Changes if Discord asks.
You can only move roles that sit below your own highest role, so the owner is the one who should do this. On mobile, the Roles screen has its own reorder option. If you can't find it, do this step on desktop. Also remember that no bot can ban or kick the server owner, so Wick protects the server from everyone else, not from the owner's own account. Turn on 2FA for the owner account.
Step 3: Run Wick's setup
Wick's docs on its site describe two ways to do the first setup: a setup command in a channel, or a step-by-step wizard on the Wick dashboard. The wizard is easier if you haven't used Wick before.
During setup, Wick may create its own roles and log channels. Afterwards:
- Go back to Server Settings > Roles and check that any role Wick created (for example, one for quarantined members) sits below the Wick role.
- Make sure only staff can see the log channels.
- Read Wick's section on recovering access if the owner gets locked out. Do this before you set strict limits, not after.
Step 4: Set anti-nuke limits
An anti-nuke limit means "if one account does X actions within Y time, punish it." The usual actions are bans, kicks, channel deletes, role deletes and webhook creation. Set limits based on your busiest normal moment, not an average day:
- Channel and role deletes: keep these strict. Nobody needs to delete many channels in a minute during normal running.
- Bans and kicks: go looser. During a raid, a mod might ban a handful of accounts quickly. If the limit is lower than that, Wick punishes your own mod in the middle of the cleanup.
- Punishment: start with quarantine, or with removing the person's roles, rather than a ban. You can undo those if you set a limit too low.
Some of Wick's deeper protections, such as extended anti-nuke and anti-raid, are Premium. See wickbot.com for what your plan includes.
Step 5: Whitelist trusted admins and bots
This is the step most people skip, and it's the reason ticket bots and auto-role bots get quarantined. In the Wick dashboard, add to the whitelist (Wick's newer versions call these permits) the accounts you listed earlier:
- Co-owners and the most senior admins.
- Ticket bots, because they create and delete channels quickly.
- Auto-role and reaction-role bots, because they give out roles in bulk. If you use Dyno for this, see how to set up Dyno auto roles.
- Any bot that creates temporary voice channels or restores backups.
Whitelist as few accounts as you can. If a whitelisted account gets compromised, it can do damage without being stopped. Older guides use terms like "Extra Owners" or a "V5 flag" step. Follow what the current dashboard shows instead.
Step 6: Turn on Wick verification
Verification makes new members prove they are real before they can see the server. Turn it on in Wick's verification settings, then fix the Discord side so it actually gates people:
- Create (or let Wick create) a verified role.
- In each channel's permissions, take View Channel away from @everyone and give it to the verified role.
- Leave one verification channel visible to @everyone.
- Check that the verified role sits below the Wick role in Server Settings > Roles.
Wick's verification flow has changed over time, so guides from earlier years may describe steps that no longer match. Use the current dashboard. For the general pattern with any bot, see our verification bot setup guide.
Common Wick fixes
- Wick can't ban or quarantine someone. The target's highest role is above Wick's, or level with it. Move Wick to the top (step 2).
- "Lacks permissions" errors. Wick is missing a permission, or a channel override is blocking it. Give the Wick role Administrator, or re-invite it with the permissions it asks for.
- Wick punished my ticket bot or auto-role bot. Whitelist that bot (step 5), then restore its roles.
- There is no Wick role. Kick Wick and re-invite it with permissions ticked.
- New members can see everything. @everyone still has View Channel somewhere. Check category permissions too, not just individual channels.
- I'm locked out of Wick's settings. Use the recovery steps in Wick's docs on wickbot.com.
A simpler option: PeakBot Security
If you want security in the same dashboard as your welcome messages, tickets and levels, PeakBot does that. PeakBot's Security page has anti-nuke and anti-raid: thresholds on mass bans, kicks, channel deletes and role deletes, join-rate and account-age limits, a quarantine role, auto-unlock, a whitelist and a threat log. Everything is set on the web dashboard. There is no setup command.
- Add PeakBot from peakbot.pro and follow Getting started.
- Drag the PeakBot role to the top in Server Settings > Roles. The same Discord rule applies to every bot.
- In the dashboard sidebar, open Security, set your thresholds and add trusted staff and bots to the whitelist.
- Open Verification to post a panel with a button, add optional questions, set the unverified and verified roles, and turn on an auto-kick for people who never verify.
- Open Backups. The free plan keeps one daily snapshot of your server's structure, and paid plans keep more.
Where Wick does better: security is all it does, and it has heat-based automod. If security depth is your only priority, Wick fits that well. PeakBot fits if you'd rather run one bot for security, verification and the rest of your community features.
Frequently Asked Questions
Does Wick need Administrator permission?
Not strictly, but a security bot has to act everywhere. Administrator bypasses channel overrides, which stops a lot of "lacks permissions" errors. Whatever you grant, its role position matters just as much.
Why is Wick kicking or quarantining my ticket bot?
Ticket bots create and delete channels fast, and that looks like a nuke. Add the ticket bot to Wick's whitelist, then give back any roles it lost.
How do I whitelist an admin in Wick?
Use the whitelist or permits section of the Wick dashboard and add the user. Whitelist only people you fully trust, and make sure they use 2FA.
How do I turn off Wick verification?
Turn it off in Wick's verification settings. Then give View Channel back to @everyone, or new members will be stuck seeing only one channel.
Is Wick free?
Wick has a free tier. Anti-raid, extended anti-nuke and backups are Premium. Current pricing is on wickbot.com.
Can I run Wick alongside another security bot?
You can, but two anti-nuke bots can mistake each other's cleanup for an attack. Whitelist each bot in the other, or pick one bot for security.
