Members are still in my server but lost the verified role
Your member count looks fine, yet people are messaging you saying they can't see a single channel. They didn't leave. Something switched their access off, and it's almost always the same thing.
Short answer
They removed your bot from Authorized Apps in their Discord settings. Discord notifies RestoreCord, which marks them unauthorized and reverses their verification based on your role mode. They stay in the server; clicking verify again restores their access immediately.
What actually happened
When someone verifies, they approve your bot in a Discord authorization screen. Later, they can take that back under User Settings → Authorized Apps. Plenty of people do it while tidying up their account, without realising what it's connected to.
The moment they do, Discord sends a deauthorization event to RestoreCord. RestoreCord then does three things for every server that member verified in:
- Marks them as unauthorized in your member list, so they're no longer counted as someone you can pull.
- Reverses their verification roles, following the on-verify action you chose for the server.
- Records a deauthorization event and, if you set a webhook, posts it to your log channel.
How your role mode decides what they lose
Every RestoreCord server has an On Verify Action. The reversal simply undoes it:
| Your on-verify action | On verify | After a deauthorization |
|---|---|---|
| Give role | Verified role added | Verified role removed |
| Remove unverified role | Unverified role taken away | Unverified role given back |
| Both | Verified added, unverified removed | Verified removed, unverified given back |
So if your channels are locked to the verified role, or hidden from the unverified role, the member suddenly sees nothing. From their side, it looks like they were kicked.
Why RestoreCord does this on purpose
Access should match consent. If someone withdraws permission, the perks that permission unlocked go with it.
There's a practical reason too. A member who revoked access can't be pulled into a server any more, so leaving their verified role in place would make your server look safer than it is. Reversing it keeps the verified role honest: the people holding it are the people you can actually bring back.
The fix: let them verify again
Nobody needs to rejoin. The member clicks your verify button once more, approves the bot, and RestoreCord gives their access back. Make that obvious with a pinned note in your verify channel. Feel free to copy this one:
Lost access to the server? Nothing's wrong with your account.
If you removed our bot under User Settings > Authorized Apps,
Discord switched off your verification too.
Fix it in ten seconds:
1. Scroll up to the verify message in this channel
2. Click Verify and approve the bot
3. Your roles come straight backIf the verify channel itself is locked to verified members, people who lost the role can't reach the button. Make sure it's visible to @everyone or to your unverified role.
Spotting it early
Deauthorizations are part of member event tracking on every plan, Free included, so a sudden cluster shows up in Analytics. On Business and above, scheduled OAuth authorization checks also re-check members' authorization on a schedule you pick, from hourly to monthly.
Seeing a real drop in numbers too? Start with the member drop diagnosis, or head back to RestoreCord Member Loss.
Sort out a lost verified role
Confirm it's a deauthorization
Check member event tracking for deauthorization events around the time people started asking.
Check your role mode
Know whether your server removes a verified role, adds back an unverified role, or both.
Post a re-verify note
Pin a short, friendly message in your verify channel explaining what happened.
Let them verify again
Members click verify, approve the bot, and their access returns on the spot.
Before the next wave of confused members
Four quick checks so people can fix it themselves.
Verify channel is visible to unverified members
If the people who lost their role can't see the verify message, they can't fix it themselves.
Bot role sits above the verified role
RestoreCord needs to be higher in the role list to give the role back after they verify.
Webhook log points at a staff channel
Deauthorizations are sent to your server's webhook, so staff see them as they happen.
Mods know the one-line answer
"You removed the bot's access, click verify again." Saves a dozen confused tickets.
Verified role questions
Keep your verified role meaning something
RestoreCord ties access to real consent, so the people holding your role are the people you can bring back.