Block suspicious accounts before they verify

#What the Join Gate does

The Join Gate looks at every account the moment it joins, before it can do anything on the server. Verification is the step a member has to pass. The Join Gate is a step earlier: it decides whether an account is even allowed to reach the verification panel, or should be stopped at the door.

It runs three checks, always in the same order: No avatar, then Account age, then the Ad-name filter. The first one that matches decides what happens, and the rest are not checked.

#The three checks

Each check looks at one thing about the account. You turn on the ones that fit your server and leave the rest off.

• No avatar. The account has no profile picture, only the default grey silhouette. Real people usually set one within minutes, so a fresh account with no avatar is the most common shape of a throwaway or a bot.
• Account age Premium. The Discord account was created less than a number of days ago, which you set (1 to 365). This is aimed at the accounts made minutes before joining, the kind a raid runs on. Older accounts pass.
• Ad-name filter Premium. The username itself looks like an advert or a scam: a link, an invite, wording like free nitro, giveaway, a promo code or a 50% off. These accounts carry their spam in the name, so they can be caught before they type a word.

The order is fixed and it matters. An account with no avatar that is also brand new is stopped by No avatar first, and the log shows that reason. So if a member is caught, the reason you read is the first check they failed, not the only one they would have failed.

#Choose what happens

Each check has its own action, the thing Easy Auth does to an account that fails it. There are four, and the same four are offered for every check:

• Off. The check does nothing. This is how you keep a check turned off: there is no separate switch, the action is the switch.
• Kick. The account is removed from the server. It can come back and try again later, so this stops the account now without shutting the door for good.
• Ban. The account is removed and cannot rejoin. A member caught by mistake cannot get back in on their own.
• Verification Blocked. The account stays in the server but cannot verify itself. Only your team can let it through, from the log entry or with /verify. Nobody is removed, so a member caught by mistake is one click away from being let in.

#Set it up

Everything is in /settings → Join Gate. Pick an action next to each check you want on, and leave the others on Off. There is no master switch to turn the Join Gate on: a check is live the moment its action is set to anything other than Off.

The Join Gate section, with all three checks on. No avatar and the Ad-name filter are a single dropdown each. Account age opens a small form where you type the number of days and pick the action together. The Premium marks the two Premium checks.

The two Premium checks appear on every plan, but stay locked until the server is Premium. A value you set while Premium stays saved after it ends, yet the check does not act again until Premium is back, so nothing you configured is lost.

#Let trusted accounts skip the gate

A strict gate will sometimes point at someone you actually want in: a friend on a brand new account, a partner with no avatar. The whitelist is the way around it. A whitelisted account is verified the instant it joins, before any check runs, so it skips the Join Gate entirely.

You manage it with /whitelist add, /whitelist remove and /whitelist list. The useful part is that you can add an account by its ID before it has joined, so you can clear a new account that has no avatar ahead of time and let it walk straight in.

#Where you see it, and members already in

Every account the gate stops writes a Join Gate blocked entry in your log channel. It names the check that failed, one of No profile picture, Account too young or Advertising username, and whether the action went through: Action taken or Action failed, followed by Kicked, Banned or Blocked (staff verification only).

If a kick or ban cannot be carried out, Easy Auth falls back to Locked instead: the account cannot self-verify, which is the same as a block. This happens when Easy Auth is missing the matching permission, Kick Members or Ban Members, or when the account sits higher than Easy Auth in the server role list. The guide on why a kick or ban fails walks through both.

The Join Gate only acts on accounts as they join. It never touches members who are already in your server, even ones who would fail a check you just turned on. To find those, run /reconcile: it reports the current members who would not pass the gate now, for your team to review, and it does not punish anyone. Acting on them is left to you.