A calm offboarding routine for Discord staff
Most server disasters involve someone who used to be trusted. A short, boring routine for staff exits removes most of that risk, and RestoreCord covers the parts Discord doesn't.
Short answer
Take a fresh RestoreCord backup first, remove the person from Sub-Users on every server, strip their Discord staff roles, and rotate the bot token, API keys and firewall passwords they could have seen.
Before the conversation
Create a backup. If anything goes wrong in the next hour, you want a recovery point from right now, not from last week. On Business and Enterprise, also check that your scheduled backups actually ran recently, and pin the newest good snapshot so rotation can't remove it.
Then check the members side: your verified member list is what lets you rebuild in a replacement server if the worst happens. If verification has been switched off at any point, turn it back on now.
Remove dashboard access
In Manage → Sub-Users, open the person's row menu and choose Remove. Their access to that server ends immediately. Their own RestoreCord account isn't touched, and neither are other servers they help with, so repeat this on every server where they had access.
Manage Sub-Users
Share server access with other users.
Remove Discord permissions
In Discord itself, take away their staff roles, then audit what's left:
- Any role with Administrator, Manage Server or Manage Roles
- Webhooks they created in your channels
- Bots or integrations they added
- Invite links they own that you still rely on
Rotate anything they could see
| Secret | Where to rotate it |
|---|---|
| Bot token | Reset it in the Discord Developer Portal, then paste the new one into the bot's credentials in RestoreCord |
| API keys | Revoke their integration's key under Account and create a new scoped key |
| Firewall password | Change it in the server's firewall settings |
| Your own password | Change it under Account → Security if it was ever shared |
While you're in Account, review Sessions and sign out any device you don't recognise. Shared logins tend to leave old sessions behind.
Harden for next time
Turn on two-factor authentication for your own RestoreCord account under Account → Security; once it's off, anyone holding the password gets in. In Discord, consider Require 2FA for moderator actions (Server Settings → Safety Setup → Moderation) so nobody can ban, kick or time out members without 2FA. If you switch it on, the bot owner's Discord account needs 2FA too, or the bot can no longer hand out the verified role.
And if your team still shares a login, this is the moment to move everyone onto individual sub-user accounts. Offboarding a sub-user is one click; offboarding a shared password means changing it for everyone. If the person who left also owned the bot, read who should own your bot before anything else.
Tell the rest of the team
Keep the announcement short and factual: who has left the team, who now covers their duties and where staff should report anything unusual. Avoid sharing details of the reasons in public channels. If the departure was not friendly, ask your remaining moderators to flag new accounts that behave like the person who left; with alt detection on Premium and above, RestoreCord can surface those matches at verification.
The week after
Watch your verification logs and member events for a few days. If something does go wrong, you have a snapshot from before the conversation and a list of verified members you can pull into a replacement server. Restore the structure, pull members back, then run Restore Roles; the role mapping is kept for 7 days after a restore.
Back to RestoreCord for Owners.
The offboarding checklist
Snapshot first
Create a backup of the server before you tell anyone, so you have a recovery point from this exact moment.
Remove dashboard access
Remove the person from Sub-Users on every server they had access to.
Strip Discord permissions
Take away staff roles and check for anything with Administrator, Manage Server or Manage Roles.
Rotate shared secrets
Reset the bot token, API keys and firewall passwords they could have seen.
Offboarding questions
Make staff changes a non-event
RestoreCord gives you backups, scoped access and recoverable members, so one departure can't take the community with it.