Who should own your Discord bot and RestoreCord account?
The most fragile part of many communities isn't the firewall or the backups. It's the single person whose account everything quietly hangs off. Here's how owners take that key-person risk off the table.
Short answer
Put the RestoreCord account and the bot's Discord application in hands the community controls, ideally a dedicated owner account or a Discord application team, both with 2FA. Give staff their own sub-user seats and give integrations their own expiring API keys.
The quiet single point of failure
Communities grow informally. A co-founder creates the bot from their personal Discord account, someone else registers the dashboard, and three moderators learn the password. It all works until one of those people burns out, gets their account compromised or leaves angry. Then you discover the community doesn't own the things it runs on.
RestoreCord's own bot security guidance puts it first on the list: don't let a personal Discord account own the production bot. A dedicated owner or a Discord application team should control it.
Map what you depend on
List every asset the community can't run without, who controls it today and who should:
| Asset | Who should control it | Why it matters |
|---|---|---|
| Bot's Discord application | A dedicated owner account or a Discord application team | Whoever owns it can reset the token or delete the bot |
| RestoreCord account | The community's owner account, with 2FA | It holds your servers, snapshots and verified members |
| Staff dashboard access | Each person's own sub-user seat | Removing one seat doesn't disturb anyone else |
| Integrations | A named API key per job | You can revoke one integration without breaking the rest |
| Discord server ownership | The same person or entity as the above | Ownership is the last word on everything |
Move the assets, one by one
The bot
If the bot lives on a personal account, move it to a team the community controls in the Discord Developer Portal, then reset the token and paste the new one into the bot's Bot Credentials in RestoreCord. Keep the bot single-purpose: RestoreCord's guidance is to use it only for verification and recovery, not giveaways or experiments.
The RestoreCord account
Enable two-factor authentication under Account → Security. While you're there, check Sessions for devices you don't recognise; a password that was once shared usually left a few behind.
Staff
Replace the shared password with sub-users, available on Premium, Business and Enterprise. Each teammate signs in as themselves, and no permission lets them manage other sub-users. Our permissions guide has a starting setup per role.
Integrations
Give every script or service its own key, created in the dashboard with:
- A name that says which job it belongs to
- The shortest expiration that still works
- Only the permissions the integration needs
- An IP allowlist when it runs on fixed infrastructure
Keys go in the Authorization header from server-side code only, never in a browser bundle or a Discord message.
If your Discord server has Require 2FA for moderator actions turned on, the bot owner's Discord account must have 2FA as well. Without it the bot can't assign roles, so new members verify but never get the verified role. Check this right after you move the bot.
Write a one-page succession note
Finally, write down where each asset lives and who can reach it if you're unavailable for a month. Store it somewhere private that a trusted deputy can open. It's the cheapest continuity measure there is, and it pairs naturally with a recovery drill and a tidy staff offboarding routine. Back to RestoreCord for Owners.
Personal accounts versus business-held accounts
The same setup, owned two different ways.
| Held by one person | Held by the community | |
|---|---|---|
| Survives that person leaving | — | |
| Staff access | One shared password | A sub-user seat each |
| Removing one teammate | Change the password for everyone | One click, one server |
| Bot token resets | Only if they cooperate | Whenever the owner decides |
| Integrations | Run on the owner's login | Separate expiring API keys |
Account ownership questions
Make the community the owner
Seat your team as sub-users, lock the owner login with 2FA and keep the bot in hands that stay. RestoreCord handles the rest.