Step 4: the RestoreCord go-live checklist
You have a bot, a server and a verification message. Before you tell your community, run through this list. It takes a few minutes and catches nearly every setup mistake.
Short answer
Join with a spare account and verify end to end, confirm Join Scope is enabled so members can be added back later, take and preview your first snapshot, then announce verification and make clear staff will never ask for passwords.
Test like a newcomer
Your own account has admin rights and sees everything, so it can't tell you what a new member experiences. Use a spare Discord account with no roles.
- Join the server with the spare account.
- Confirm it can see the verification channel and nothing it shouldn't.
- Click Verify and approve on Discord's authorization screen.
- Check that the expected role was added, or removed, depending on your role mode.
- Confirm the account can now see the channels a member should see.
If the role didn't change, the bot's role is almost certainly too low, or it's missing Manage Roles.
Make sure members can be recovered
Check that Join Scope is enabled for your server. It requests the guilds.join scope, which allows the bot to add verified members to a server later. Without it, a member pull has nothing to work with.
Save a day-one snapshot
Click Create Snapshot on your server card. Give it a name you'll understand later, like Initial setup. When it finishes, open it in the previewer and check your channels and roles are there. A padlock on a channel means the bot couldn't read it.
Snapshot captured before the permission redesign.
Roles and overwrites look right in the preview.
Backup completed — 42 channels, 18 roles, 6,300 messages.
| Plan | Snapshots per server | Automatic |
|---|---|---|
| Free | 1 | No |
| Premium | 5 | No |
| Business | 30 | Yes |
| Enterprise | 50 | Yes |
If the first verifications go wrong
| What you see | Check first |
|---|---|
| No verification message in the channel | Run /setup in the channel, or republish from the dashboard |
| /setup missing from the command menu | Restart Discord, then try again |
| Verified but no role | Bot role position and the Manage Roles permission |
| Newcomers see every channel | Protected channels still allow View Channel for @everyone |
| Snapshot button greyed out | No custom bot is attached to the server |
Fix the first problem on the list and test again with the spare account before moving to the next one.
Tell your members
A short announcement makes verification feel like protection rather than a chore. Cover three points:
- Why you're asking: so the community can be restored if the server is ever lost.
- How it works: one click and Discord's own authorization screen.
- What staff will never do: ask for passwords, tokens or logins.
Post the verification link only in your own channels. After launches, copycat links sometimes circulate, so tell members where the real one lives.
Optional next steps
| Add this | For | Plan |
|---|---|---|
| VPN blocking and alt detection | Stopping ban evaders and raid accounts | Premium and up |
| Sub-users | Letting staff help without your login | Premium and up |
| Scheduled snapshots | Backups that take themselves | Business and up |
| Webhook logs | Verification events in a staff channel | All plans |
Compare everything on the RestoreCord pricing page. Need to redo an earlier step? See step 1: your bot, step 2: your server or step 3: verification.
Go live in four checks
Join as a newcomer
Use an account with no roles and confirm it only sees the verification channel.
Verify end to end
Click Verify, approve on Discord and check that the role was added or removed as planned.
Snapshot the server
Create a snapshot named Initial setup and open it in the previewer.
Announce verification
Explain why you're asking members to verify and where the real link is.
Go-live questions
Setup done. Community protected.
With verification live and a first snapshot saved, every new member who verifies with RestoreCord is recoverable.