Ten minutes from "I have a Discord server" to "AutoMod is on, logs are routed, and verification works." Last updated .
From the bot page, click Invite. Discord will ask which server to add the bot to and which permissions to grant. The bot requests Administrator; the why-Administrator note on the overview explains the reasoning. If you'd rather invite with a narrower scope, get in touch via the contact form — some features will be disabled but most will still work.
After inviting, Discord creates an apoptotic role. Drag it
above any role the bot needs to manage. If you intend to use
BMC tier sync or verification-driven role assignment, the bot's role must be
above the roles it will assign or remove. If you intend to moderate users with
higher static roles (for example owner-tier roles), the bot cannot enforce
actions against them — Discord prevents lower roles from acting on higher ones.
apoptotic distinguishes Moderator from Admin:
/config role moderator <role> — users in this role can use moderation commands (/warn, /mute, etc.)./config role admin <role> — users in this role can use server-wide configuration commands (/automod, /log, /level-role, etc.).Pick existing server roles. The bot does not create them for you, by design — it is your role hierarchy, not the bot's.
Create the channels you want the bot to log into and route the categories:
/log channel messages #log-messages/log channel members #log-members/log channel roles #log-roles/log channel channels #log-channels/log channel voice #log-voice/log channel automod #log-automod
You can route several categories to the same channel if you'd rather not have
six. Run /log status to see the current routing.
AutoMod ships off; turn the layers on one at a time:
/automod phishing on — the lowest-effort, highest-value win./automod spam 5 5 — five messages in five seconds is a reasonable starting threshold; tune from there./automod mentions 5 — caps each message at five @mentions./automod links deny + /automod links allow <your-domain> — start strict and allow what you trust, rather than the other way around./automod raid on and /automod nuke on — opinionated heuristics; revisit if you see false positives.
Use /automod status to confirm the active chain.
/verify (optional)
The /verify flow is opt-in alt-account detection. It only acts on
users a moderator explicitly verifies; there is no implicit "every new join is
verified" mode. The flow is described in detail in the
apoptotic case study and in the
website privacy policy — both of these are
worth reading before you turn it on so you can answer member questions.
/config verify channel <channel> — where verification results are posted (admin-only by default)./verify @user; the user receives a DM with the link.If your community uses BMC, map each tier to a Discord role:
/bmc tier-role "Coffee" @Coffee/bmc tier-role "Latte" @Latte
Members link their BMC membership themselves with /bmc link <email>.
The bot polls and reconciles roles automatically; no manual intervention is needed
when a member upgrades, downgrades, or cancels.
Once the bot is configured, admins can also work through the dashboard. Sign in with Discord at dashboard.apoptoses.com; after the OAuth round trip you'll see only the guilds where you hold the admin role configured in Step 3.
/ping — should reply with gateway and HTTP latency./about — should reply with version info./level — confirms leveling is recording XP./log status — confirms the routing.If anything misbehaves, the contact form is the fastest way to get help.