Why members lose their roles after a restore, and how to fix it
You restored the server, pulled everyone back, and now nobody has their roles. That's not a bug. It's how Discord works, and RestoreCord has a dedicated step for it.
Short answer
A restore recreates roles with new Discord IDs, so old assignments don't carry over. RestoreCord saves each member's role mapping for 7 days. Pull your members back, then run Restore Roles from the dashboard banner to hand everyone their old roles.
Why the roles disappear
Every Discord role has an ID. When RestoreCord restores a snapshot, it recreates your roles with the same names, colours and permissions, but Discord gives each one a new ID. Member role assignments point at IDs, not names, so returning members arrive with none of their old roles.
RestoreCord solves this by recording which member had which role and re-mapping those assignments onto the recreated roles. That mapping is kept for 7 days after the restore.
The order matters
Discord can only give a role to someone who is already in the server. That's why the recovery happens in a fixed order:
- Restore the snapshot so channels, categories and roles exist again
- Pull verified members back into the restored server
- Run Restore Roles from the dashboard banner
412 members have roles waiting to be restored · 968 role assignments · Expires in 6d 21h
Roles are recreated with new IDs; each member's saved roles are re-mapped and queued for 7 days.
“Pending Role Restore” shows on the dashboard with member and assignment counts.
Roles can only be assigned to members already in the server.
Runs in the background at Discord-safe rates; cancel any time, assigned roles are kept.
Run Restore Roles too early and anyone who isn't back yet stays pending until the data expires. If a pull is still running, let it finish first.
Why it isn't instant
Restore Roles hands roles back gradually, to stay inside Discord's rate limits. On a big server this can take a while, and that's deliberate: a bot that hammers the API gets throttled and finishes later, not sooner.
Check the bot role first
The bot can only assign roles below its own. After a restore, check that your bot's role is above every role it needs to hand back, staff roles included. If it isn't, roles above it will be skipped. The role order guide explains how to fix it in a minute.
What comes back, and what doesn't
| Item | How it returns |
|---|---|
| Channels, categories, permissions | From the snapshot restore |
| Roles themselves | Recreated by the restore, with new IDs |
| Members | Through a member pull, for members who verified |
| Member role assignments | Through Restore Roles, within 7 days |
| Message history | Re-posted up to your plan's limit, not as the original authors |
The 7-day window starts at the restore, not at the pull. If you're rebuilding in stages, schedule the pull and the role restore inside the same week.
A note on staff roles
Staff roles come back through the same mapping, which is convenient and worth thinking about. If someone was removed from your team shortly before the incident, their old role assignment may still be in the snapshot. After Restore Roles finishes, open your staff roles in Discord and check that every holder should still have it. It's a two-minute review that closes a quiet gap.
The same goes for any role with Administrator or Manage Server. A rebuilt server is a good moment to tighten permissions you'd been meaning to clean up anyway.
Prepare before you need it
Role recovery depends on two things you set up in advance: a recent snapshot that includes your current roles, and members who verified so they can be pulled back. On Business and Enterprise, scheduled backups take care of the first. Verification takes care of the second.
Want a cleaner member list in the rebuilt server? Read how smart filters work, or browse the RestoreCord Blog.
Roles back in three steps
Rebuild from the snapshot
Rebuild channels, categories and roles from your backup into the target server.
Pull members back
Start a member pull so verified members rejoin the restored server.
Hand roles back with Restore Roles
Use the dashboard banner within 7 days so returning members get their old roles.
After Restore Roles finishes
A short review that catches the gaps a rebuild can leave behind.
Every pulled member has their roles
Spot-check a few long-time members. Anyone still missing roles may have rejoined after Restore Roles ran.
Staff roles are held by current staff
The mapping restores old assignments, so remove roles from anyone who left the team before the incident.
Admin-level roles are tightened
Review every role with Administrator or Manage Server while the rebuilt server is still quiet.
The bot role is still above managed roles
Recreated roles can land in a new order. Check it before the next verification or pull.
A fresh snapshot exists
Take a new backup of the rebuilt server so your next restore starts from today's structure.
Verification is live again
Send a test verification with a second account so new joiners become restorable from now on.
Restore Roles questions
Recover the server and the hierarchy
RestoreCord restores your structure, brings members back and re-maps their roles, all from one dashboard.