RestoreBase Docs
Set up your workspace, connect your Discord bot, publish a branded member flow, and run operations from the dashboard.
Hosted-first docs
These docs are written for the real RestoreBase workspace flow. Most teams do not need to clone the repo or manage infrastructure to get value from the product.
RestoreBase is a managed Discord bot platform for communities that want their own bot identity, branded verification flow, protection controls, and member continuity in one workspace.
Members verify once through Discord OAuth, operators manage the live member flow from the dashboard, and the same system stays ready for exports, policy review, and member restore if an incident ever happens.
Start Here
1. Getting Started
Sign in, follow the launch checklist, and reach the first live verification test.
2. Discord Setup
Create the Discord app, save the callback, and invite the bot into the right server.
3. Workspace Setup
Connect the bot, attach the server, configure verification, and run the hosted flow.
4. Operations
Learn what operators actually do after launch, from roster checks to continuity actions.
This Is A Service, Not A Local Install Guide
Most RestoreBase customers do not install the repo, set environment variables, or deploy anything themselves.
Your setup happens inside the hosted dashboard:
- sign in to your workspace
- connect your Discord bot on
/custom-bots - attach the server on
/servers - configure the member flow on
/verification - confirm member readiness on
/membersand/reports
If you are part of the RestoreBase team or handling a deeper technical rollout, the repo still matters for source control, internal development, and service changes. That is secondary to the normal customer setup flow documented here.
If RestoreBase has already provisioned a workspace for you, you can ignore repo-level setup instructions entirely.
How The Product Actually Works
- Workspace admins sign in at
/loginor create an account at/signup. - In
/custom-bots, you save the Discord application details for the bot you want RestoreBase to use. - In
/servers, you attach the Discord server that bot can already see. - In
/verification, you choose the verification channel, verified role, and member-facing copy. - Members complete the Discord OAuth flow through the generated verification link or the published Discord message.
- RestoreBase stores the resulting authorization state and verified member record.
- Later, operators use
/members,/reports, and related workspace pages to run continuity actions, restore members when needed, and review workspace health.
Main Workspace Areas
/dashboard
Launch checklist, health summary, and recent operator activity.
/custom-bots
Discord app credentials, bot identity, and callback details.
/servers
Attach the exact Discord server that the selected bot can already see.
/verification
Control the verification channel, role, copy, and member-facing flow.
/members
Manage verified members, remove stale entries, and run continuity actions.
/reports
Coverage, readiness, and verification analytics for workspace health.
What You Should Have Ready
- access to your RestoreBase workspace
- access to the Discord Developer Portal for the bot you want to connect
- permission to invite that bot into the server you want to protect
- the channel and role you want to use for verification
- a real member account you can use for one live end-to-end test