Documentation

FAQ

Common RestoreCord questions about verification, member restore, bots, snapshots, firewall rules, and API access.

Copy page

General

What does RestoreCord back up?

RestoreCord stores member authorization records from verification and can create snapshots for server structure where backups are available.

Does RestoreCord replace Discord permissions?

No. Discord permissions, role hierarchy, OAuth scopes, and rate limits still control what can happen.

Should I use a dedicated bot account?

Yes. A dedicated Discord application and bot reduce blast radius and make credential rotation easier.

Members and Restores

Can every member be restored?

Only members with valid stored authorization can be pulled. Members who never verified or revoked authorization need to verify again.

Why do pulls take time?

RestoreCord has to respect Discord API rate limits. Large pulls can complete gradually instead of instantly.

Do snapshots restore members?

No. Snapshots restore saved server structure. Member restoration uses the pull workflow.

Bots and Permissions

Why does bot role position matter?

Discord prevents a bot from assigning or managing roles above its own highest role.

Can I delete a bot from RestoreCord?

Yes, but RestoreCord blocks deletion while any server still uses that bot.

What OAuth scope is needed for adding members?

Member adding and later pulls require the guilds.join scope.

API and Webhooks

How do API keys work?

API keys use the format keyId.secret, can be restricted by permission bitfields, and can be limited by IP or CIDR allowlists.

Are API keys full account sessions?

No. API keys are scoped for automation and do not expose sensitive account operations such as password or session management.

What is the difference between webhook logs and webhook events?

Webhook logs post to Discord channels. Enterprise webhook events are signed HTTP deliveries to your own systems.

Next Steps

API Keys

Create scoped automation credentials.