The complete RestoreCord setup, in four numbered steps

This is the walkthrough for owners who want every click spelled out. You'll build your own bot, connect your server, publish a verification message and run a test, ending with a server whose members can be brought back.

Every step works on the Free plan. No code required.

The route from empty dashboard to verified members

Do them in order. Each step depends on the one before it, and each has its own detailed guide on this site.

  1. Build your custom bot

    Open Bots in the RestoreCord dashboard, choose Add New Bot and let the wizard check your bot token, client secret and redirect URL.

  2. Add the Discord server

    Open Servers, choose Add new server, select the Discord server, name its verification link and pick Give Role, Remove Role or Both.

  3. Publish the verification message

    Run Set up verification for a reviewed channel plan and a generated message, or post the message yourself with /setup.

  4. Test, snapshot and announce

    Verify with a spare account, confirm the role changed, save a first snapshot and tell your members where the real link lives.

Begin with your bot

See each step before you do it

Flip through what the dashboard and Discord show you at every stage, with example values in place of yours.

A wizard that checks your homework

Add New Bot opens the right pages of the Discord Developer Portal and confirms the token, client secret and redirect URL the moment you paste them.

  • Your name and avatar on the authorization screen
  • Slash commands load without manual registration
  • Full walkthrough: create your bot

Bot Credentials

Sensitive information used to authenticate your bot

Bot Token
••••••••••••••••••••••••••••••••
Client Secret
••••••••••••••••••••••••

Valid Redirect URL

Step three only touches what you approve

Channel permissions scare most owners off verification. RestoreCord reads your channel names, categories and overwrites, proposes a plan, and changes a single permission, View Channel, on the channels you tick.

  • Admin, mod, ticket and log channels are never protected
  • Original overwrites are saved as a baseline first
  • A failed run rolls itself back and flags Needs attention
Publish verification step by step
Text Channels
rules
verify
general
media
staff-chat
mod-logs
Verification channel
Where the verify message is posted.
Public
Explicitly visible before verifying.
Protected
Hidden until the member verifies.
Unchanged
Permissions left exactly as they are.

Your go-live checklist

Tick these off before you post the announcement. Each one maps to a step above.

Bot listed in the dashboard

Your custom bot shows in Bots and has been invited to the server.

Server and role saved

The server card shows your role mode and the role RestoreCord manages.

Bot role sits high enough

It's above the verified or unverified role in Server Settings, Roles.

Verification message posted

It's in a channel unverified members can actually see.

Join Scope enabled

Required so verified members can be added back to a server later.

Spare-account test passed

The role changed and the member channels appeared.

First snapshot saved

Named something clear like Initial setup, and checked in the previewer.

Announcement written

It says where the real link is and that staff never ask for passwords.

Want the deep version of the final step?

The go-live guide covers spare-account testing, a fix table for first-day problems and what to add once you're running.

Open the go-live guide

Before you start the walkthrough

Four steps. One sitting. A recoverable server.

Create your free RestoreCord account and work through the walkthrough from step 1. By the end, everyone who verifies can be restored.