From the Verify button to the verified role
Members see a button and a Discord screen. Behind them, RestoreCord runs a short, fixed sequence that decides whether they get in. Knowing the order makes every support question easier.
Short answer
The member opens your verify page, passes any gates you set (age prompt, captcha, password), approves your bot on discord.com, is checked by your firewall and then receives the verified role from your bot.
1. Two ways in
Most members start from the verification message in your Discord channel. Its Verify button is published as a {verify_url} link, which goes straight to Discord's authorisation screen for your bot. Others arrive from a link you shared on a website or social profile. That link opens your verify page first, with your icon, name, description, badges and whatever styling your plan allows, and the Verify button sits on the card.
The page answers to your server name, to your server's Discord ID and to tracking link codes, so you can share whichever form suits the place you post it. If the server is marked as NSFW, the icon and description stay hidden until the visitor confirms they're an adult; that answer is remembered for a week.
2. Optional gates before Discord
Two gates can sit in front of the Verify button on the page, and both are your choice:
- A captcha challenge, available on every plan, that slows down scripted verifications
- A verification password, part of the Enterprise firewall password system, for servers that hand out access codes
A wrong password or a skipped captcha stops the flow right here, with a message telling the member what to do.
3. Discord's authorisation screen
Discord shows your bot's name and the permissions it requests. The member logs in and approves on discord.com, so their password never reaches RestoreCord. Which scopes appear depends on your settings:
| Scope | Why it's requested | When |
|---|---|---|
| identify | Tells RestoreCord which Discord account is verifying | Always |
| guilds.join | Lets your bot add the member to a server later, the basis of member recovery | When Join Servers For User is on |
| guilds | Lists the servers the member is in | Business setting, or any active server-membership rule |
| Reads the account's email address | When you save emails, or any active email-domain rule |
Keep the scope list short if you can. When a server only asks for identify and guilds.join, returning members who already approved that bot pass without seeing the screen again. Adding guilds or email means everyone sees the screen every time.
4. The progress screen and the firewall
After Authorize, Discord returns the member to your verify page, which shows a short progress screen while your firewall works. The messages appear in this order:
- Connecting to Discord
- Checking your connection
- Confirming you're not a robot
- Granting server access
Behind it, every check you've switched on runs: blacklists, VPN and proxy detection, alt detection, server-membership rules and custom rules. Each one lets the member continue or stops them with a specific reason. If Discord is busy, the screen says so and asks them to try again in a moment instead of failing silently.
Blocked members never receive a role, so they can't see your channels. Your staff can review each decision in the firewall activity log.
5. The role, and the backup
If everything passes, your bot gives the verified role, removes the unverified role, or does both, depending on what you picked during setup. The page confirms it, or forwards the member to your Redirect After Verify URL on Business. Their authorisation is stored for your server at the same moment, which is what lets RestoreCord bring them back after a raid, a takeover or a deleted server.
Walk it yourself
Keep a spare Discord account that isn't staff, open your verify link in a private window and note each screen. Repeat after you change the verified role, the bot or a firewall rule. If something breaks, the verify page error guide tells you whose side the fix is on, and the styling guide covers how the page itself looks.
The flow at a glance
Gates on the page
An age prompt for NSFW servers, then a captcha or verification password if you've switched them on.
Discord authorisation
The member approves identify and any other scopes your settings request on discord.com.
Firewall decision
Blacklists, VPN and alt checks and your custom rules either let the member through or stop them with a reason.
Role and confirmation
The bot adds or removes the role you chose and the page confirms the member is verified.
Member flow questions
Try the flow on your own server
Set up RestoreCord, verify from a spare account and watch each step happen.