Members are back but have no roles? Here's why

You restored the snapshot and pulled everyone in, and now the whole server is grey. That's expected, and RestoreCord already saved what you need to fix it.

Short answer

A restore recreates roles with new Discord IDs, so old assignments can't carry over. RestoreCord maps each member's saved roles to the new IDs and keeps that mapping for 7 days. Pull members back first, then run Restore Roles from the Pending Role Restore banner.

Why roles don't survive a restore by themselves

Every role in Discord has an ID, and a member's roles are stored as a list of those IDs. When a snapshot restore recreates your roles, Discord issues new IDs. The old list now points at roles that no longer exist, so a member who rejoins arrives with nothing but @everyone.

RestoreCord handles this for you. During the restore it records which old role became which new one, and translates every member's saved roles to the new IDs. That mapping is kept for 7 days and appears in the dashboard as a Pending Role Restore banner.

Pending Role RestorePending

412 members have roles waiting to be restored · 968 role assignments · Expires in 6d 21h

Step 1
Backup restore finishes

Roles are recreated with new IDs; each member's saved roles are re-mapped and queued for 7 days.

Step 2
Banner appears

“Pending Role Restore” shows on the dashboard with member and assignment counts.

Step 3
Pull members first

Roles can only be assigned to members already in the server.

Step 4
Run Restore Roles

Runs in the background at Discord-safe rates; cancel any time, assigned roles are kept.

Why the order matters

Discord only lets a bot give a role to someone who is already in the server. Run the role restore before people are back and most of it has nothing to do. Bring them back with a member pull first, then hand out roles.

  1. Finish the snapshot restore so every role exists again.
  2. Start a member pull into the server and let it run.
  3. Open the Pending Role Restore banner and start Restore Roles.
  4. Follow progress under Running Tasks in the dashboard.
  5. Pull late arrivals and run it again before the 7 days are up.

When some roles are skipped

The role restore reports anything it couldn't assign instead of failing quietly. The usual causes:

Reported asCauseFix
Missing permissionThe bot doesn't have Manage RolesGrant it, then run the restore again
Role above the botThe bot's own role sits below the role it's assigningDrag the bot's role near the top of the list
Integration roleThe role belongs to another bot or a server subscriptionThose are assigned by the integration, not by you
Deleted roleSomeone removed the role after the restoreRecreate it and assign it manually

Why are some roles missing permissions?

Discord bots can only assign roles positioned below their own role in the server hierarchy.

Server Settings>Roles
Admin
Moderator
Member
RestoreCord
BOT
Move RestoreCord above Moderator

Go to Server Settings → Roles in Discord and drag RestoreCord above the role you want to assign.

Stopping and restarting

You can cancel a running role restore. It stops after the current batch, keeps the roles it already gave, and leaves the rest pending. That's useful if you notice the bot's role is in the wrong place halfway through: cancel, fix the hierarchy, and start again.

Deleting the pending role data is permanent. Once it's gone, every role still waiting has to be handed out by hand, so leave it alone until you're sure everyone who's coming back is back.

Checking the result

When the task finishes, open the role restore details and read the skipped list rather than assuming everything went through. Spot-check a few members whose roles matter most, such as moderators, event hosts or paid tiers, and compare them with what you expected. Anything still missing is usually down to role order, which you can fix and then run again while the window is open.

Once roles look right, take a fresh snapshot. Your next recovery point then includes the corrected assignments instead of the broken state you just repaired.

Members who can't be pulled

Only people who verified through RestoreCord before the incident can be pulled, and Discord still decides on each add. For everyone else, post a fresh invite through your announcement channels and socials. When they rejoin and verify, assign their roles manually or through your normal onboarding.

If you haven't restored yet, start with the first hour after a nuke, or go back to RestoreCord Recovery for the full order.

Give everyone their roles back

  1. Pull members in first

    Discord can only give a role to someone who is already in the server, so bring people back before anything else.

  2. Run Restore Roles

    Open the Pending Role Restore banner in the dashboard and start it. Progress shows under Running Tasks.

  3. Mop up the stragglers

    Pull anyone who arrived late and run it again before the 7-day window closes, then handle skipped roles by hand.

Read the Pull Members guide

Missing role questions

Recover the roles, not just the room

RestoreCord saves who had what, so your community comes back with its ranks, colours and access intact.