Easy Auth
/settings → Verification

Set up verification in 5 minutes

Setting up Easy Auth is mostly work inside Discord, hiding your channels from unverified members, and only a minute in the bot itself.

1. Create the verified role

Easy Auth doesn't create roles: it hands out one you already have. Keep it plain, with no permissions of its own. The access it grants comes from step 2.

  1. In Server Settings → Roles, click Create Role and call it something obvious, like Verified.
  2. Leave every permission off, then Save Changes.
  3. Drag it below the Easy Auth role and save again. A bot can only hand out roles below its own, so see the guide on the verified role.

2. Set the two server-wide defaults

Two switches in Server Settings → Roles are enough: turn View Channel off for @everyone, and on for Verified. From then on the server is hidden by default, and the role is what reveals it.

  1. Open @everyone, search for view channel, turn it off and Save Changes.
  2. Open Verified, search for the same permission, turn it on and save again.

Server Settings → Roles

view channel

@everyone

View Channel

@Verified

View Channel

From now on nobody can see the server until they have the role. The next step restores access to the one channel everyone needs.

3. Open the verification channel to everyone

One text channel, visible to everyone, where the verification panel lives. Call it #verify.

  1. Open Edit Channel → Permissions on #verify.
  2. Add @everyone and set View Channel to , so anyone who joins can reach this channel.
  3. Set Send Messages to for the same role. Nobody needs to type here.
  4. Add Verified and set View Channel to , so the channel disappears once someone is verified.

#verify → Permissions

@everyone

View Channel

Send Messages

@Verified

View Channel

Anyone who hasn't verified sees this channel, and can only read it.

Easy Auth needs access to this channel

The bot posts the panel here, so the cross above applies to it too. Unless Easy Auth has Administrator, add it to this channel and give it View Channel, Send Messages and Embed Links on , or the panel can't show up.

Any other channel you want people to read before verifying, like #rules, gets the same treatment.

4. Leave every other channel alone

There is nothing to do here. Every other channel and category stays as it is, with both roles on : unverified members cannot see them, verified members can. This is what the two switches in step 2 give you.

Community (category) → Permissions

@everyone

View Channel

@Verified

View Channel

There is also nothing to redo when you add a channel later.

Staff channels need two exceptions

Anything meant only for your team (staff chat, moderation, the Easy Auth log channel) would otherwise open up to every verified member. On each of those channels, set View Channel to for Verified, and to for your staff role (Moderator, Admin, whatever you call it). Your team keeps access, nobody else gets in. Do this before you hand the verified role to anyone.

The three states, once and for all. Getting them wrong is the most common reason a setup breaks:

  • Denied: a no here, no matter what the role can do elsewhere.
  • Inherited: no answer here, so the role's own setting applies. That's what step 2 set.
  • Allowed: a yes here, even for a role that can't do it anywhere else. It's what makes #verify visible to members with no role.

Before verifying

Start here

  • verify

Information

  • rules
  • announcements

After verifying

Information

  • rules
  • announcements

Community

  • general
  • off-topic

Why not do it all with an unverified role?

Because the role has to be assigned first, and that depends on Discord. If the Discord API fails, or the bot is restarting, the role may not be assigned. A server that relies only on an unverified role could let new members reach everything. With permissions, new members see nothing by default, whatever Discord is doing. An unverified role is still useful as an extra layer, but it should never be the only thing protecting the server.

5. Now set up the bot

The server is closed and the role exists. Now tell Easy Auth which role to hand out, and where: run /settings and open Verification.

  1. Method: choose the one that suits your server. The guide on methods explains what each one asks of your members.
  2. Verification channel: pick #verify. The panel gets posted there for you, and it follows the channel if you move it later.
  3. Verified role: pick Verified, the one from step 1.
  4. Enable verification: the main switch, and the last one to turn on. Nothing happens until you do.

The switch will not turn on until the method you picked can actually be used: Password needs a password, Quiz needs at least one question in the pool. Easy Auth tells you which piece is missing rather than letting you close your server by accident.

Your-Server — Settings

GeneralVerificationJoin GateLogs
Enable verification

Method

Button

Verification channel

verify

Verified role

Verified

The switch sits at the top of the panel, but leave it for last.

Then run /diagnose. It checks your setup without changing anything, and tells you if something is missing: a role, a channel, permissions, the panel. If everything is green, the setup is complete and the next member is handled automatically.

If your server already had members before you added Easy Auth, the bot never saw them join. Run /reconcile once to give them all a record and the unverified role in a single pass. The guide on reconciling members explains what it does.

6. Optional settings

Verification works without these two. Most servers add them anyway, and each is a single field.

  • Log channel, in /settings → Logs: every join, verification, failed attempt and block, written to a channel you pick, with who, when and why. Keep it visible to your staff only. What the log channel tells you.
  • Unverified role, in /settings → Verification: given on join, removed when they verify. Useful only if you prefer to show new members a read-only server rather than nothing at all. Your server is already closed without it.

Still stuck after the guide?

Ask in the support server: bring your server ID and what the bot did instead of what you expected. Billing, refunds and account issues start there too.

Ask in the support server