A Discord admin went rogue. Here's how to take the server back
Nobody broke in. Someone you trusted with Administrator decided to tear the place down, and they know exactly where everything is. Recovery looks a little different when the threat was already inside.
Short answer
Remove the rogue admin's Discord roles and their RestoreCord sub-user access at the same time, delete anything they added, and reset any credential they could have seen. Then restore a snapshot from before their first destructive change, pull members back, run Restore Roles and rebuild staff permissions on least privilege.
Why an inside job is harder than a hack
A stranger who phishes the owner account has to learn the server as they go. A staff member already knows which channels matter, which roles carry weight and which bots hold which permissions. They may also have quietly prepared: a webhook planted weeks ago, a second account given a role, a copy of the bot token from a pinned staff message. Containment has to cover all of that, not just the obvious account.
Assume anything the person could see, they still have. Rotate it.
Cut their access everywhere at once
Do these together, ideally within a few minutes, so the person can't react to one change by using another way in:
- Remove their roles in Discord, and ban them if the damage was deliberate. Check for alt accounts they gave roles to recently.
- Remove them as a RestoreCord sub-user under Dashboard → Servers → Manage → Sub-Users. Access to that server ends immediately.
- Delete webhooks, integrations and apps they added. The audit log shows who created what.
- Reset the bot token if they ever had access to it, then paste the new one into Dashboard → Bots and save.
- Change any shared passwords or API keys they could have read, including ones posted in staff channels.
Don't announce the removal in a staff channel before it's done. If they still read that channel, the announcement is their cue.
What their RestoreCord access allowed
Sub-users are scoped per server and per permission, so check which ones this person held. It tells you what else might need repairing, and which permissions to hand out more carefully next time.
Manage Sub-Users
Share server access with other users.
| Permission they held | What they could have done | What to check |
|---|---|---|
| Manage Backups | Restore over the live server, edit or delete snapshots | Whether your recovery points still exist |
| Create Backups | Take and view snapshots, but not restore or delete them | Any new snapshot taken mid-sabotage |
| View Member Details | See member IPs, emails, location and device | Treat it as a data exposure and act accordingly |
| Pull Members | Start member migrations | Migration history for pulls you didn't plan |
| Manage Firewall | Change firewall rules and passwords | Rules or passwords you don't recognise |
| Manage Settings | Change server settings, except sub-users | Verification and logging settings |
Rolling back the damage
Pick the right recovery point
Insiders often sabotage slowly: a permission changed here, a channel hidden there, before the big deletion. Scroll the audit log back to the first change that wasn't legitimate, not just the dramatic one, and restore a snapshot from before it. If they had Manage Backups, confirm the snapshot you want still exists before planning around it. A snapshot you pinned earlier is a good sign, because scheduled backups never rotate pinned ones away.
Rebuild people and ranks
If they banned members, unban them before pulling. Then run the restore, pull verified members back and hand out roles from the Pending Role Restore banner, the same sequence covered in the first hour after a nuke and restoring roles after a restore. Don't restore the rogue admin's own staff role to anyone until you've decided who should hold it.
Rebuild staff access on least privilege
The snapshot brings your old role permissions back exactly as they were, including whatever made this possible. Before reopening, go through every staff role and ask what each person actually needs. Moderators rarely need Administrator. In RestoreCord, give teammates the narrowest permissions that cover their job: Create Backups instead of Manage Backups for someone who only takes snapshots, and View Members instead of View Member Details unless they handle investigations.
Sub-users need Premium or higher. On a Free plan there's only the owner login, which is a reason never to share it with staff in the first place.
Once roles are fixed and the server is calm, take a new snapshot and pin it. The full recovery order is on the RestoreCord Recovery home page, and if the person also had the bot token, follow the token reset guide.
Staff access audit, before you reopen
Discord roles trimmed
Administrator sits with the owner and one or two people at most. Moderators get the specific permissions their job needs.
Sub-user permissions scoped
Each RestoreCord teammate holds only what they use. Manage Backups and View Member Details stay with trusted staff.
Pinned known-good snapshot
One snapshot from a calm week is pinned, so a schedule can never rotate it away while you're still finding the damage.
Bot owned by a team, not a person
The Discord application behind your bot is controlled by a dedicated owner or a Developer Portal team, not one staff member's personal account.
Bot guild list reviewed
Manage Bot Guilds shows every server your bot sits in. Leave any you don't recognise.
Offboarding written down
When someone steps down, their Discord roles and their sub-user access are removed on the same day, by the same person.
Rogue admin questions
Give staff exactly what they need, nothing more
RestoreCord sub-users let your team run snapshots and pulls without the owner login, scoped permission by permission.