Step by step guide
Nine steps, five minutes: add the bot, put its role in the right place, run the automatic setup, then fine-tune the rest. Every step shows the exact Discord screen you should see.
9 steps about 5 minutes
Step 1 of 9
Click Add to Discord, choose your server, leave the permissions ticked and confirm.
You need the Manage Server permission on that server. The requested permissions are the ones the protections need: without them, Protector sees attacks but cannot stop them.
Do not untick anything: every permission maps to a protection (ban, manage roles, manage channels, read the audit log).
Step 2 of 9
Open Server Settings, then Roles, and drag the Protector role above every other role.
On Discord, a role can never act on a role placed above it. This is the most important step: left at the bottom, Protector can neither sanction an administrator who turns hostile nor restore the roles deleted during an attack.
The "Protector" role is created when the bot joins. You cannot move it above your own highest role: put it right below.
Step 3 of 9
In any channel, type /autoconfig and send it. Discord suggests the command as you type: pick the one from Protector.
The answer is visible to you only.
/autoconfig
Step 4 of 9
Protector asks for the server language, then for a level: light, standard or strict. The level only changes how severe the thresholds are, never how many protections run.
It then creates what is missing: a log channel, a verification portal, and it turns the modules on. You can run the command again later: whatever already exists is reused, with no duplicates.
When in doubt, pick "standard". Everything stays adjustable afterwards, threshold by threshold.
Step 5 of 9
/diagnostic reviews every protection and tells you what it is missing: a permission, the role position, a channel that is not set.
While a line is red, that protection does not fully work. Fix it, then run the command again.
/diagnostic
Step 6 of 9
/autoconfig already posted the portal. To set it up by hand, or to change the mode, run /verification-setup.
A newcomer gets a quarantine role that only sees a single channel. They press the button (or copy an image captcha), get the verified role, and the server opens up. Raid bots stay at the door.
/verification-setup
Step 7 of 9
Everything Protector does is written in the log channel created at step 4: sanctions, blocked attacks, configuration changes.
The Event log module adds the server activity itself (deleted messages, granted roles, edited channels), category by category, with a dedicated channel if you want to split them.
Keep that channel for your team: it holds the names of sanctioned people and the details of every attack.
Step 8 of 9
Open /config, the General section. That is where you set the language, the log channel, the staff roles exempt from automatic protections, and the security role.
The security modules (anti-raid, anti-nuke, anti-spam, anti-webhook, bot quarantine, coordinated raid) are reserved to the server owner. The security role shares that right, and only you can grant it: if somebody else hands it out, Protector takes it back at once and warns you.
/config
Step 9 of 9
Everything /config offers is also on the dashboard: thresholds, durations, channels, roles, event log, multi-server network. Both are equivalent, and every change is still recorded in your log channel.
Two common settings to finish with: the welcome message (with its background image, available on the website only) and your server's reports channel.
A greyed out module on the website is either protected (owner and security role) or part of a Premium plan.
Protector now watches joins, messages, channels and roles. You can explore the documentation, or open the dashboard to fine-tune.
