Know the moment someone hands out a risky Discord permission
Run /auditmonitor setup and EvaluBot alerts a staff channel, the server owner, or both, when someone grants Administrator or another risky permission, lowers a server protection, transfers ownership, mass-deletes channels and roles, or starts doing damage, and when Discord detects a raid. Each alert names who made the change and how to undo it. EvaluBot never undoes anything itself.
A text or announcement channel to post alerts in. EvaluBot needs View Channel, Send Messages and Embed Links there. Setup names anything missing, and warns when members without staff permissions can read the channel.
ping_role
A staff role to ping with each alert. EvaluBot refuses @everyone and bot roles, and warns if the role cannot be mentioned.
dm_owner
Also DM the server owner. On by default. Only the owner can turn it off, and then only they can turn it back on. While it is off, EvaluBot never DMs them about alerts.
/auditmonitor statusSettings, delivery checks, EvaluBot's place in the role list, the approved Administrator list, the last alert, who last changed the settings, and the last delivery problem
/auditmonitor testA test alert to each destination, at most once every 30 seconds
/auditmonitor adminsServer owner only: approve which roles and bots hold Administrator, so alerts and reports point out anyone new
/auditmonitor offTurns alerts off, which is announced so it cannot happen quietly
staff-alertsSample
EvaluBotAPPToday at 9:41 PM
@Moderators
CriticalA role was given risky permissions
The role @Event Helpers now has Administrator.
Changed by
@jordan
If this was not expected
In Server Settings > Roles > Event Helpers, turn off anything the role does not need.
EvaluBotAPPToday at 9:43 PM
@Moderators
HighA webhook was created
Captain Hook in #general. Anyone with a webhook's link can post in that channel under any name and picture.
Created by
@sam
If this was not expected
Delete it in Edit Channel > Integrations > Webhooks, then check Server Settings > Audit Log.
EvaluBotAPPToday at 9:47 PM
@Moderators
HighA server protection was lowered
2FA for moderator actions was turned off
Changed by
@riley
If this was not expected
Restore it in Server Settings > Safety Setup, then check Server Settings > Audit Log.
What triggers an alert
Every kind of risky change, and attacks.
Critical changes can hand over or wreck the whole server, and every server gets them. High ones widen who can moderate, post or manage, and come with Premium.
CriticalAny role gets Administrator, including a new role or a newly added bot's role. A bot's alert says whether Discord has verified it
Critical@everyone gets a takeover permission: Administrator, Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Kick Members, Ban Members, Timeout Members, or Mention @everyone, @here and All Roles
Critical@everyone is allowed, in a channel, to Manage Channel, Manage Permissions, Manage Webhooks or Mention @everyone
CriticalA member is given a role that has Administrator
CriticalThe server's ownership is transferred. Only the owner can do this, so with owner DMs on, the previous owner is DMed as well as the current one
CriticalDiscord detects a raid or DM spam against members, checked every 5 minutes. The alert says whether invites or DMs are paused
Critical5 or more channels, roles, emoji, stickers or soundboard sounds are deleted within a minute, the pattern of a server being wrecked. Further deletions in the next 10 minutes go into one follow-up alert with the total
Critical10 or more channels or roles are created within a minute, the pattern of spam channels from a compromised account or bot
Critical5 or more members are banned, kicked or pruned within a minute
CriticalOne account doing damage, fast or slow: deletions, bans, kicks, timeouts and prunes build up heat, and the alert names the account and lists what it did. Ticket and temporary voice bots closing what they opened never alert
CriticalSomeone doing damage within an hour of being given Administrator or a staff permission, or a bot doing damage minutes after it was added
CriticalA security or moderation bot is removed: a well-known one, one whose role had Administrator or a staff permission, or one named Security, Guard, Anti-nuke, Shield or Moderation
CriticalEvaluBot loses a permission, or loses its place at the top of the role list. Sent to the owner by DM as well, even with owner DMs off, unless the owner turned them off
HighA role gets Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Ban Members, Kick Members, Timeout Members or Mention @everyone
High@everyone gets an elevated permission: Manage Expressions, Manage Nicknames, Manage Messages, Manage Threads and Posts, Manage Events, Mute Members, Deafen Members, Move Members, View Audit Log, View Server Insights, Priority Speaker or Bypass Slowmode
High@everyone is allowed, in a channel, to Manage Messages, Manage Threads and Posts, Manage Events, Mute Members, Deafen Members, Move Members or Priority Speaker
HighA member is given control of a channel by an override of their own: Manage Channel, Manage Permissions, Manage Webhooks or Mention @everyone there
HighA private channel is opened up: a channel @everyone could not see becomes visible to everyone, or to a booster, server subscription, Linked or integration role, often because it was synced with a public category
HighA member is given a role with any of the high role permissions above. After one alert, members given the same role in the next hour are named together in one alert when the hour is up, up to 25
High2FA for moderator actions is turned off, or the verification level or media content filter is lowered
HighThe vanity invite is removed or changed, since the old link is then free for anyone to claim
HighAn incoming webhook is created, since anyone with its link can post under any name and picture. One alert per creator per hour, and any more they make in that hour are listed together in one alert when the hour is up
HighAn AutoMod rule is turned off or deleted
HighA bot is added, with whether Discord has verified it
Inside an alert
Everything you need to act, in one message.
01
What changed
A title, and the role, channel, member or setting involved, with the permissions added. Administrator alerts say whether the holder is on the owner's approved list.
02
Changed by
Who made the change, from the audit log. This needs View Audit Log; without it, role, channel, server protection and bulk ban alerts still arrive with the author marked unknown.
03
The reason
If the person who made the change entered one in Discord, it is included.
04
If this was not expected
The exact Discord settings path to undo the change yourself. A role anyone can get, by boosting or a subscription, is called out.
How alerts behave
Only permissions being added alert. Removing one never does, except from EvaluBot's own role.
Giving EvaluBot's own role a permission, Administrator included, never alerts, since its install link asks for Administrator.
A role that already had Administrator gains nothing new, so changing it does not alert.
Attack alerts need View Audit Log, because only the audit log says who acted. EvaluBot's own actions never count.
Bulk and one-account alerts name any server protection switched off in the 15 minutes before.
After every restart or outage, however short, EvaluBot reads back each server's audit log at its next start, up to its newest 500 entries, and checks what happened meanwhile, up to a day back, so damage while it was down still alerts. Alerts still waiting to go out when it stopped are picked up the same way.
EvaluBot re-checks its own permissions and place in the role list every 5 minutes, so a change made while it was reconnecting still alerts.
Related changes within a few seconds arrive as one alert. A category edit that updates ten channels is one message. When EvaluBot shuts down, what is waiting goes out first.
A server gets at most 5 alert messages a minute. Beyond that, changes are held and sent together, critical ones first.
One delivery shows up to 9 alerts, critical ones first. In a flood of changes, a note names what had no room, with how many of each kind of change and the titles of up to 5 alerts, and points to the audit log for the rest.
The server owner is not DMed about changes they made themselves, unless posting in the alert channel fails, and never when they turned owner DMs off themselves.
Tamper notices
Any change to the alert settings by someone other than the owner is DMed to the owner, and turning alerts off or moving them to another channel is also announced in the old alert channel. Nobody can silence the alerts without your staff hearing about it.
If posting in the alert channel fails, the alert goes to the owner by DM with a note saying why, unless the owner turned owner DMs off themselves. Alert contents are not stored. On Premium, a 30-day log keeps each alert's title and severity, and who dealt with it.
Coverage
Critical alerts free. Every alert on Premium.
Free servers get every critical alert, attack detection included. Premium servers get all of them. On a free server, every alert's footer says it is critical-only.
FreeThe critical alerts, attack detection included
Alert control
On Premium, decide where alerts go.
Route each severity, keep track of who dealt with what, and catch slow drift. Changing the routing or pinning a new baseline is posted in the alert channel and sent to the owner, so nobody can quietly silence alerts.
/auditmonitor routing
A channel per severity
Send critical and High alerts to their own channels, mute High alerts on a topic, and set quiet hours when High alerts still post but do not ping. Critical alerts, and anything about an attack or EvaluBot itself, cannot be muted and always ping, since those are what an attacker would silence first. If one channel cannot take an alert, only that alert goes to the owner by DM.
/auditmonitor log
Acknowledge, with a log
Each alert carries an Acknowledge button, in the channel and in the owner's DMs, for the owner, members with Administrator or Manage Server, and the role alerts ping. When the alerts include a critical one, only the owner, Administrator or Manage Server can press it. The log lists the last 15 alerts from the last 30 days and who dealt with each. Muted alerts are recorded too, so muting never hides that something happened.
/auditmonitor baseline pin
A permission baseline
Pin how the server's roles, and what @everyone can do in each channel, should look. Every hour EvaluBot compares the server with it and alerts once about each new set of differences, so it also catches what changed while it was offline and what built up slowly.
/auditmonitor digest
A weekly digest
A summary once a week, with no ping: the week's alerts by severity and how many nobody dealt with, the latest score and its change, whether the server matches its baseline, and the month's audits. It uses no audit.
Alerts, not an anti-nuke bot.
EvaluBot tells your team what happened and who did it, so a person decides what to do next. It works alongside whatever moderation bot you already run, and its alerts never use EvaluBot's access to change your server.
Does EvaluBot undo or block risky permission changes?
No. EvaluBot only alerts. It never reverts, blocks or punishes a change, and it is not an anti-nuke or moderation bot. Each alert gives the exact settings path so your team can undo the change.
Who receives permission alerts?
Whoever you choose in /auditmonitor setup: a staff channel, the server owner by DM, or both, optionally pinging a staff role. At least one destination is required, and the owner DM is on by default. If posting in the channel fails, the alert goes to the owner by DM with a note saying why, unless the owner turned owner DMs off themselves.
Does EvaluBot need View Audit Log for alerts?
It is what lets alerts name who made each change. Without it, role, channel, server protection and bulk ban alerts still arrive with the author marked unknown, but members being given roles, new webhooks and bots, AutoMod being switched off, kicks, prunes, deleted emoji, stickers and sounds, and attacks cannot be detected.
Does EvaluBot catch a server being nuked?
It alerts on it. Mass deletions and creations, members removed in bulk, one account doing damage, fast or slow, someone doing damage right after being given power, and a security bot being removed are all critical alerts on every plan. EvaluBot never stops or reverts the attack itself.
Will permission alerts flood my staff channel?
No. Related changes within a few seconds arrive as one alert, a server gets at most 5 alert messages a minute, and repeat alerts for the same role, the same webhook creator or a mass deletion are folded together. Removing permissions never alerts. On Premium you can also send each severity to its own channel, mute High alerts on a topic, and set quiet hours.
Can someone turn the alerts off without anyone noticing?
No. Any change to the alert settings by someone other than the owner, including the ping role, is DMed to the owner, and turning alerts off or moving them is also announced in the old alert channel. Only the owner can stop their own alert DMs. Changing alert routing or pinning a new baseline is posted in the alert channel and sent to the owner, and critical alerts can never be muted.
Can I see which alerts my team has dealt with?
On Premium, yes. Each alert has an Acknowledge button that then shows who pressed it. The role alerts ping can press it, except on critical alerts, which need the owner, Administrator or Manage Server. /auditmonitor log lists the last 15 alerts from the last 30 days with who dealt with each. Add unacknowledged:true to see only the ones nobody has.
What if EvaluBot was offline when something happened?
It still alerts. After every restart or outage, however short, EvaluBot reads back each server's audit log at its next start, up to its newest 500 entries, and checks what happened meanwhile, up to a day back. On Premium, the permission baseline also catches changes that built up while it was away.
Are permission alerts free?
Yes. Every server gets the critical alerts, attack detection included. Premium adds every other risky change: other risky permissions, server protections being lowered, new webhooks and bots, AutoMod rules being turned off, the vanity invite changing, members given control of a channel, and private channels opened up.
Turn on alerts in one command.
Add EvaluBot, run /auditmonitor setup, and pick a staff channel. Critical alerts and attack detection are free on every server.