Security
Thirteen modules that protect your server from nukes, raids, spam and impersonators, with quarantine, logging and a trust system for your staff.
- Dashboard
- Dashboard › Security
- Commands
/security settings, /security whitelist, /security lastactions, /mod quarantine- You need
- Server owner, or an Extra Owner or Trusted Admin the owner adds. Administrator alone isn't enough.
- Element needs
- Administrator is the simplest choice. At the least: Manage Roles and Manage Channels (for quarantine), View Audit Log, plus whatever each module acts with, like Kick, Ban or Moderate Members.
What it does
Security is a set of modules you switch on one by one. Every module starts off.
| Module | What it does |
|---|---|
| Anti Nuke | Protects the server from malicious actions by members or bots, like mass bans or deleting channels |
| Anti Raid | Tracks new member activity to spot and stop raids |
| Auto Mod | Detects and prevents spam, advertising and other unwanted behaviour |
| Join Gate | Manages which new members and bots are let in |
| Verification | Asks new members to solve a captcha before they can see the server |
| Lockdown | Puts the server into lockdown modes during raids or emergencies |
| Anti Impersonation | Checks names and avatars against members with dangerous permissions |
| Protected Roles | Adds extra protection to the roles you choose |
| Image Checking | Detects and responds to known images using perceptual hashes |
| Logging | Logs the events you choose to the channels you choose |
| Reports | Lets members report messages and users to your staff |
| Unauthorized Text Channel Deletions | Recovers the last messages of a channel deleted without permission |
| Dank Pool Protection | Protects your server's Dank Memer pool from abuse |
When a module catches someone, it acts as you set it: usually quarantine, which strips the member's access until staff review it, or a timeout, kick or ban.
Why use it
A compromised admin account or a malicious bot can delete every channel and ban every member in seconds. Security watches for that and stops it, and handles the day-to-day spam, raids and scams too.
Who can change it
Security has its own trust levels, separate from Discord permissions:
- The server owner can do everything.
- Extra Owners (up to 5) can change every setting, including Trusted Admins.
- Trusted Admins (up to 8) can change most settings.
Extra Owners and Trusted Admins are completely immune to Security, so only give these levels to people you fully trust. Add them on the dashboard's People tab, or the Authority members page of /security settings.
If the owner loses access, Element sends them a recovery key by DM. e!recoversecurityaccess in DMs uses it to get back in.
Set it up
- Open the dashboard, pick your server and go to Security. The Overview lists every module.
- Set up Logging first, so you can see what the other modules do.
- Add your Extra Owners and Trusted Admins on the People tab.
- Switch on modules one at a time, starting with Anti Nuke.
- Run
/security settings, or jump to a page with its page option, likelogging. - Set up Logging first, so you can see what the other modules do.
- Add your Authority members.
- Switch on modules one at a time, starting with Anti Nuke.
The security guide walks through a safe order with the commands.
Commands
| Command | What it does |
|---|---|
/security settings | Open the settings, on the overview or the page you pick |
/security whitelist | Exempt a member, role, channel, category or webhook from some or all checks, optionally for a while |
/security lastactions | Show recent audit log actions, by member or action |
/mod quarantine | Quarantine a member by hand |
/mod unquarantine | Lift a quarantine |
Every command needs the owner, an Extra Owner or a Trusted Admin. Members who try them without access are reported in the security log.
Common problems
- "You are not allowed to manage Security". Only the owner, Extra Owners and Trusted Admins can. Administrator isn't enough.
- Quarantine doesn't work on someone. Element can't manage members whose top role is at or above its own. Move Element's role up, ideally to the top.
- A trusted bot keeps getting caught. Whitelist it with
/security whitelist, for just the checks it trips. - Nothing seems to happen. Check the module is switched on: every module starts off.
Turn it off or reset it
Switch modules off on their pages in /security settings. Whitelists can be given a duration so they end by themselves.