Verification Gate

The Verification Gate keeps lurkers and raid accounts out of your server until they click a button. New members only see your verify channel; one click grants the verified role and opens the rest of the server.

Until September 2026 the gate was part of the Welcome plugin. It is its own plugin now, so you can use it without welcome messages, and switch it on or off on its own. If you used it before, your settings, your verify message and its button moved over unchanged — and if the gate was running, the plugin was switched on for you. The Verification Gate doesn't take one of your free plugin slots.

Set it up

1. Enable Verification Gate in the Plugin Market, or with the switch at the top of its page.
2. Open the Verification Gate page (under Moderation in the sidebar).
3. Pick the Channel for the verify message and the Verified role that a click grants.
4. Optionally pick an Unverified role. Every new member gets it on join, and loses it once verified.
5. Word the message yourself with Embed title, Embed text and Button label (see below), then save.

Saving posts the message in the channel. Change anything later and save again — CloudMod edits the same message instead of posting a new one.

Write the message

The page shows a live preview next to the form: the message exactly as it will look in Discord, with your title, text, button and colour. It updates while you type.

• Templates. Pick Friendly community, Gaming server or Rules + introduction (Quest mode) to fill in a title and a set of rules, then edit them. If you already wrote a text, CloudMod asks before replacing it, and nothing is saved until you save.
• Embed text. Your rules or instructions, up to 4,000 characters. Discord formatting works: bold, italic, lists and ## headings. Leave it empty and the message shows only the title and the button.
• Colour. Pick a colour or type a hex value like #5865F2. Network default uses your Branding colour, or CloudMod's blurple.
• Post again. If the message was deleted or the channel was cleaned up, Post again deletes the old message and posts a fresh one.

The CloudMod watermark

Without the Branding Pack, the message carries CloudMod's footer and a small CloudMod button next to the verify button. The preview shows both. The Branding Pack removes them — on any plan — and unlocks your own colour, logo and footer. Networks on Network or higher don't show the watermark either. When your branding or plan changes, CloudMod updates the message by itself within a few minutes; you don't have to save.

Deadline for unverified members

Many servers write "whoever hasn't verified after a week is removed" into their rules. The gate can do it for you. Switch on Deadline for unverified members, pick the number of days (1 to 30), and save.

• Anyone who has no verified role after that many days is kicked — never banned, so they can join again. About a day before, they get a DM that tells them how to verify.
• The clock starts when someone joins — or when you switch the deadline on, for members who were already on the server. Nobody is removed before their full time has passed.
• Never removed: bots, the server owner, admins and the people you listed as project admins or on the trusted list, and anyone who can kick, ban, manage roles or time out members.
• In quest mode, a member who accepted the rules but hasn't written the introduction yet still counts as unverified.
• It needs a verify channel and a verified role, because nobody can be asked to verify without them.
• Safety stop: if a large part of the server would be warned or removed at once, CloudMod does nothing and says so in your log channel. That almost always means members who should stay don't have the verified role yet — give it to them, and the deadline carries on by itself.
• In test mode, nobody is warned or removed. Removals show up in your log channel (moderation) and in the audit log.

Before you switch it on, make sure everyone who should stay already has the verified role.

Check my setup

Open Check my setup and press Run check. CloudMod looks at your channel permissions and tells you whether a new member sees only the verify channel — the most common setup mistake. It also warns if nobody can see the verify channel, if verified members see nothing behind the gate, and (in quest mode) if the quest channel is hidden from the quest role or open to everyone. The check only reads; it changes nothing, and it uses your saved settings.

How the gate works

With an unverified role set, every new member gets it on join. Deny that role access to the rest of the server and allow it only the verify channel — then the verify channel is the only thing they can see. Clicking the button grants the verified role and removes the unverified one.

Without an unverified role, the gate works the other way round: give the verified role access to your channels and keep them hidden from @everyone.

The button survives bot restarts — CloudMod re-registers it, so old messages keep working.

Quest mode (optional)

Quest mode turns the one click into two steps, for servers that want to hear from newcomers before letting them in. It is a switch inside the Verification Gate — free, no extra plugin, and off until you turn it on.

1. The button reads Accept the rules (change it with Button label). A click grants the quest role, takes away the unverified role, and tells the member which channel to go to.
2. The member writes a short introduction in the quest channel. That message grants the verified role and removes the quest role. CloudMod adds a ✅ to the message.

CloudMod only checks that a message was written and how long it is — never what it says. The minimum length (20 characters by default; 1 accepts any message) keeps a lone "." from counting. A message the word filter removes doesn't count either.

To set it up, open Quest mode on the Verification Gate page, switch it on, pick the quest channel and the quest role, and save. Then set the channel permissions yourself, because CloudMod doesn't touch them:

• Show the quest channel to the quest role only (hide it from @everyone and from the unverified role).
• Give the verified role access to the rest of the server, as in the normal gate.

Good to know:

• The quest, verified and unverified roles must be three different roles, and all of them must sit below the CloudMod role. Both the quest and the verified role are checked when someone accepts the rules, so nobody writes an introduction that then can't be rewarded.
• CloudMod needs View Channel in the quest channel to see the introduction; it doesn't have to be able to write there. Add Reactions is only needed for the ✅.
• Turning quest mode off sends the button back to the one-click behaviour. Members who still hold the quest role are verified with their next click, and the quest role is taken away.
• Without a quest channel and a quest role the button answers that verification is not configured — it never hands out the verified role by itself.

Auto Roles and the gate

Auto Roles are given the moment someone joins. If one of them opens the channels your gate keeps closed, that member skips the gate without clicking anything. Two settings keep the two apart.

Give Auto Roles only after verification is a switch in the Auto Roles card on the Verification Gate page. It is off until you turn it on, so nothing changes for servers that already run.

• With the switch on, a new member gets the Auto Roles of your main server after they verify: with the click, or in quest mode with the introduction (accepting the rules alone doesn't release them).
• It only does something while the gate works: a verify channel and a verified role, and in quest mode also the quest channel and the quest role. Until then Auto Roles are given on join as usual, so nobody waits for a gate that can't be passed.
• Bots and members who already have the verified role get their Auto Roles right away.
• Sub-servers have no gate and give their Auto Roles on join. Role Sync rules aren't held back either, only the Auto Roles themselves.
• Switching it off doesn't hand out Auto Roles to members who are waiting at that moment, and a second click on the button never gives back a role a moderator took away.

A role of the gate can't be an Auto Role. The verified, the unverified and the quest role are greyed out in the Auto Role picker, and the gate's own pickers grey out roles that already are Auto Roles. As an Auto Role the verified role would open the server on join, and the unverified role would come back right after the click. CloudMod refuses to save such a combination — and /welcome set refuses it too. A combination that was already set up before stays editable, so you can still save other settings.

Good to know

• Bots are skipped — they never get the unverified role.
• Welcome conditions don't apply here. An account that is too young to be greeted still gets the unverified role; the gate doesn't look at welcome settings at all.
• Turning the plugin off stops the unverified role on join, and the button answers "Verification is turned off on this server right now" instead of handing out roles. The message stays in the channel, so switching it back on needs no new post.
• The verified and the unverified role must be two different roles.
• Both roles must sit below the CloudMod role, and CloudMod needs Manage Roles. Roles managed by another integration (Server Booster, a Twitch sub role) can't be handed out by any bot — Discord doesn't allow it. The role pickers mark such roles before you choose them.
• The gate runs on your main server. The Account Age Filter runs first: an account it quarantines, kicks or bans on join doesn't get the unverified role.

Requirements: Manage Roles for both roles, Send Messages and Embed Links in the verify channel.