Pick the channel
The log channel is a normal text channel that only your team can see. Easy Auth writes one message in it for every event you asked for. Until you pick a channel, nothing is recorded, so this is the first step.
- Create a channel for it, something like
#mod-logs, and make sure your members cannot see it. - Set it as the log channel from the dashboard, or with
/settings → Logsin Discord. Both write the same setting. - Give Easy Auth View Channel, Send Messages and Embed Links in that channel, unless it already has Administrator.
No permissions, no logs
/diagnose tells you if something is missing.What gets logged
There are seventeen types of entry, and each one has its own switch. Grouped by what they are about:
- Verification: Verification started, Verification success, Failed attempt, Verification failed, Blocked attempt, Unverification, Verify all.
- Protection: Join Gate blocked, Raid alert.
- Members: Member joined, Member left, Bot joined.
- Moderation: Member kicked, Member banned, Member unbanned, Member blocked, Member unblocked.
Two of them are easy to mix up. Failed attempt is a single wrong answer, and a member can produce several of them in a row. Verification failed happens once, when the member runs out of attempts or out of time, and it is the entry that carries the punishment.
Verification started is posted once per member, the first time they open the challenge, so on a busy server it is about as frequent as Member joined. It earns its place if you use a time limit or a punishment: it is the entry that proves a member really started, instead of leaving you to guess. It does not exist for the Button method, where opening the challenge and passing it are the same click.
The Moderation entries are for what a person does: a moderator kicks, bans or unbans someone, or your staff blocks a member from verifying. When the bot removes someone as a punishment, the entry that reports it is Verification failed or Join Gate blocked, which also gives the reason. The member still appears under Member left, like any other departure.
Some alerts always arrive
/diagnose. That one does not switch verification off: set the missing piece and it starts working again.How to read an entry
Every entry has the same shape. The title says which event it is, the fields say who and how, and the block at the bottom says how it ended.
- The colour of the bar is the outcome at a glance: green went well, red failed, yellow needs your attention, blue is neutral news.
- Username is a real mention, so you can click it and open the member.
- Informations lists what the bot actually did, one line per outcome. It is the part worth reading, and the next section goes through every line it can contain.
- The footer carries the member ID and the time. The ID stays valid after a name change and after the member leaves, so it is what you search by.
The fields in the middle change with the event:
- Member joined: account age, and the invite used (if available) with who created it.
- Member left: whether they were verified, blocked, and their attempts.
- Verification started: the method they were given, and how long they had been in the server before starting.
- Verification success: method, attempts, time taken, and who verified them.
- Verification failed and Failed attempt: attempts used.
- Kicked, banned, unbanned, unverified, blocked, unblocked: who did it, and the reason when given.
- Raid alert: two entries per wave and no more, one when it starts and one when it ends. The first says how it was detected and what went into force; the second how long it lasted and how many accounts were acted on.
- Verify all: who ran it, and the counts (newly verified, role re-added, skipped, errors).
Attempts reads 3/5 when you set a maximum, and just 3 when you did not. It only appears for methods where the member can get something wrong.
Method is not only the four you can choose. It also records the ways a member can end up verified without doing anything:
Password,Button,Captcha,Quiz: the member passed the challenge you set.Auto (invite),Auto (rejoin),Auto (whitelist): verified on the way in, by invite, by coming back, or by being on the whitelist.Manual (staff),Verify all: verified by your team, one member at a time or in bulk.
What the Informations block says
This is the block that tells you whether the bot managed to do what it set out to do. Most of your troubleshooting starts here, so it is worth knowing every line.
On a verification success. The first line is always Verification registered: the member is now verified in Easy Auth, whatever happens next. The second line is about the role, and it is one of two:
Verification role successfully added. The member has the verified role and can see the server. Nothing to do.Verified role NOT assigned, followed by the reason. The member counts as verified but has no role, so nothing opened up for them. The reason is usually the role sitting above Easy Auth in the list, or a missing Manage Roles permission, and the guide on the verified role covers both. Fix it, then run/verifyallto catch everyone this happened to.
A success where the role could not be assigned. The member is verified, but the second line tells you nothing opened up, and why.
On a verification failure. The first line is why it ended, one of Maximum attempts reached, Unverified time limit exceeded (since join) or Verification time limit exceeded (since start). The second line reports the punishment:
Punishment applied, followed byKick,BanorVerification blocked. It went through.Punishment failed, followed by the same value. Easy Auth is missing the matching permission (Kick Members, Ban Members) or the member sits above it in the role list. The guide on why a kick or ban fails covers both.Locked instead, the member can no longer self-verify. It appears under a failed kick or ban: the member could not be removed, so Easy Auth at least stops them from retrying.
A final failure: the reason on the first line, the punishment that was carried out on the second.
On a Join Gate block. The first line is the check that failed, one of No profile picture, Account too young, Advertising username or Raid detected. The second is what happened: Action taken or Action failed, followed by Kicked, Banned or Blocked (staff verification only). The same Locked instead fallback applies here.
On a blocked attempt. A single line saying why the member could not start, one of Verification is currently disabled, Verification locked, Join countdown not elapsed yet, Verification closed (scheduled hours) or Verification closed (raid mode).
On staff actions. Unverifications, blocks and unblocks report what happened to the member roles: Roles updated when they changed, Roles NOT updated with a reason when Easy Auth could not touch them, or Member is no longer in the server, roles were not updated. when they had already left. A block also states Member can no longer verify, staff verification required, and an unblock Member can verify again.
One line means the problem is ours
The action could not be completed due to an internal error. Please contact support. replaces the outcome line when something broke on our side rather than in your setup. It comes with a Support Server button, and it is the one case where the entry is worth reporting to us instead of fixing yourself.Entries you can act on
Some entries carry a button, so you can deal with the situation without leaving the channel.
- Verify Manually, on a blocked attempt: it verifies that member on the spot, past whatever stopped them. Only Administrators and your bot master role can use it, and it keeps working after a restart, so an old entry is still usable. If the member has left, it tells you. If they were verified in the meantime, it re-checks their role instead of verifying them twice.
- View Details, on a
/verifyallsummary or on the entry that closes a raid: the full list of members behind the numbers, shown only to you. The raid list is read back from your server history, so an old entry still opens. - Support Server: it appears on the internal error line described above.
Blocked attempts are kept quiet on purpose. The same member with the same reason is logged at most once a minute, and a member who is simply already verified is never logged at all.
Choose what to log
Each of the seventeen types has its own switch. Turn off the ones you do not read: on a busy server, Member joined and Failed attempt are usually the two that bury everything else.
Logs
The Logs screen: the channel at the top, then one switch per event. In this example Member left and Failed attempt are off, so those two never reach the channel. The same settings live in /settings → Logs inside Discord.
Every type is on when you start. Types added to Easy Auth later stay off until you turn them on, so a new release never fills your channel with something you did not ask for.
The log channel and all seventeen types are free. The channel is a stream, though, and old entries scroll away. When you need the state of one member long after the fact, run /verifyinfo on them: it reports their last verification and, if they are blocked, why and since when.