#Turn on Kick Members and Ban Members

To remove an account, Easy Auth needs the permission that matches the action: Kick Members to kick, Ban Members to ban. Without the one an action needs, Discord blocks it before the bot can even try, and no setting inside Easy Auth will change that.

Open Server Settings → Roles and pick the Easy Auth role.
Open the Permissions tab.
Turn on Kick Members and Ban Members, then click Save Changes.

Server Settings → Roles → Easy Auth

Kick Members

Members with this permission can remove other members from this server. Kicked members will be able to rejoin if they have another invite.

Ban Members

Members with this permission can permanently ban and delete the message history of other members from this server.

The two permissions on the Easy Auth role, both on. You only need the one that matches the action you set, but turning on both covers kicks and bans together.

Already have Administrator?

If Easy Auth has the Administrator permission, both of these are built in, so you can skip this step.

#Keep Easy Auth above the members it removes

Permissions are only half of it. Discord will not let a bot kick or ban a member whose highest role sits above the bot's own role, whatever permissions the bot has. So Easy Auth also has to sit high enough in the role list to cover the members you want it to act on.

Open Server Settings → Roles.
Drag the Easy Auth role above the roles your ordinary members have.
Click Save Changes.

This is the same role list you order for the verified role, seen from the other side. What counts is Easy Auth's highest role, so if you keep your bots in a shared role, moving that one is enough.

It still cannot touch your staff, and that is fine

A bot can never act on someone whose role is above its own, and you want to keep it that way: leave your admin and moderator roles above Easy Auth, so it can never remove them. The Join Gate is aimed at new and untrusted accounts, which sit at the bottom of the list, so in practice Easy Auth only needs to be above ordinary members.

#Where the failure shows up

When an action cannot go through, your log channel says so, on two kinds of entry:

On a verification failure: Punishment failed, followed by Kick or Ban.
On a Join Gate block: Action failed, followed by Kicked or Banned.

In both cases Easy Auth blocks the account instead and writes Locked instead: the account stays in the server but can no longer verify itself, so only your team can let it in. A kick or ban that fails never leaves an account free to slip through verification.

#Check that it worked

Run /diagnose in your server. It reads your setup, changes nothing, and only you can see the report. The Bot permissions line tells you whether Kick Members and Ban Members are in place.

It is a staff-only command: you need Administrator, or the bot master role you set in /settings → General.

The bot isn't kicking or banning members

#Turn on Kick Members and Ban Members

#Keep Easy Auth above the members it removes

#Where the failure shows up

#Check that it worked

Keep going

How do I fix members after the bot was offline?

Set up verification in 5 minutes

Still stuck after the guide?