Skip to main content
Logs keep your staff informed about every verification. Alerts ping a role when a check catches someone, so the right people see it right away.

​
Logs

Logs are split into modules, and each module can post to its own channel. A module without a channel isn’t logged.
The Logs card with 24 modules set upThe Logs card with 24 modules set up
Turn on Logs, then click Configure.
The Logs window, with a channel picked for each categoryThe Logs window, with a channel picked for each category
  • Every category sets one channel for everything at once.
  • Each category row sets a channel for all of its modules. Expand a row to pick a channel per module.
  • The All checkbox turns every module in that row on or off.

​
Modules

A common setup sends Successful Verifications and General Logs to a quiet channel, and every failure to a separate channel your moderators watch.

​
What a log looks like

A successful verification log showing the account and the role it was givenA successful verification log showing the account and the role it was given
Shows the member and the role they were given. If they verified with a bypass link, the skipped checks are listed too.
Logs only show what staff need. Raw IP addresses, emails, cookies, and fingerprints are never posted. See Data Collection.

​
Alerts

Alerts ping a role in a module’s logs channel whenever that check catches someone. They need Logs to be on, and a check only shows up here once its module has a logs channel.
The Alerts card with 4 alerts set upThe Alerts card with 4 alerts set up
Turn on Alerts, click Configure, and pick the role each detection should ping.
The Alerts window, with the Moderators role picked for some detectionsThe Alerts window, with the Moderators role picked for some detections
The role has to be mentionable, or AuthenticateMe needs the Mention @everyone, @here and All Roles permission in the logs channels it pings in. The Health page warns you if a role can’t be pinged.