> Why roles come back as a separate step, how RestoreCord's 7-day Pending Role Restore works, and the order of restore, pull and roles that makes it succeed.

Source: https://restorecord.rip/restore-roles-after-rebuild

# How to restore member roles after rebuilding a server

A restored server has all its roles, but nobody to give them to yet. Role restore is its own step in RestoreCord, and getting the order right decides whether it works.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)

Short answer

Restore the snapshot, pull members back into the server, then run Restore Roles from the Pending Role Restore banner. RestoreCord holds each member's role mapping for 7 days; members who aren't back yet stay pending until it expires.

## Why roles come back separately

Two Discord rules shape the whole process. First, a restore creates the roles again with **new IDs**, so an old assignment can't simply point at them. Second, a bot can only give a role to someone who is already in the server. RestoreCord handles the first by remapping every member's saved roles to the new IDs. You handle the second by bringing members back before you hand out roles.

## The order that works

1. 1Restore the snapshot into the server
2. 2Pull verified members back in
3. 3Run Restore Roles
4. 4Run it again after later waves of members return

## The 7-day window

After a snapshot restore, the dashboard shows a **Pending Role Restore** banner. The mapping behind it is kept for **7 days**. During that week you can run the role restore as many times as you need. Members who are in the server receive their roles; anyone still missing stays pending.

Pending Role RestorePending

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

View Details

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.

Deleting the pending role data is permanent. After that, any remaining roles have to be handed out by hand, so only delete it once you are sure the restore is complete.

## What the bot needs

* The Manage Roles permission
* Its own role above every role it assigns
* To stay in the server for the whole run

If your bot sits below the Moderator role, it can't give anyone Moderator. Move it up before you start, not halfway through.

### 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.

## While it runs

The role restore runs in the background at rates Discord accepts and reports progress under **Running Tasks**. If you cancel, it finishes the current batch and stops. Roles already given stay given, and the rest remain pending, so you can pick up later inside the window.

## Roles that get skipped

| Skipped role              | Why                                       | What to do                               |
| ------------------------- | ----------------------------------------- | ---------------------------------------- |
| Managed by an integration | Another bot or Discord itself controls it | Leave it; the integration reassigns it   |
| Deleted since the restore | The role no longer exists                 | Recreate it and assign by hand if needed |

## A worked example

Say your rebuilt server gets its snapshot restored on Monday. You start a member pull straight away, and by Monday evening the first big wave is in, so you run Restore Roles and those members get their roles. On Wednesday more people have come back through the pull and through your posted invite. You run Restore Roles again and they are covered too. On Sunday you do a last run. Anyone still missing after the 7 days gets their role by hand when they return.

## A careful approach for staff roles

### Why you might hold some back

If the server died because of a compromised account, giving every admin and moderator role back automatically may restore the attacker's access too. Consider removing staff roles from the server before running the restore, then handing them out personally once each account is confirmed secure.

### Tell members what to expect

Post a short note that roles return in waves as people rejoin. It saves your staff a flood of "where's my role?" messages.

Haven't restored the structure yet? Start with [rebuilding a deleted server](https://restorecord.rip/deleted-server-rebuild), or rehearse the whole sequence in a [practice rebuild](https://restorecord.rip/practice-server-rebuild). Or go back to [RestoreCord Rebuild](https://restorecord.rip/).

## Getting every role back, step by step

1. 1  
### Raise the bot's role  
Give the bot Manage Roles and drag its role above every role it has to hand out, before anything else runs.
2. 2  
### Bring members in first  
Run the member pull so people are inside the server; Discord refuses roles for anyone who isn't.
3. 3  
### Run Restore Roles  
Open the Pending Role Restore banner and start it. Progress shows under Running Tasks.
4. 4  
### Repeat for late arrivals  
Run it again after each new wave of members, then review the skipped list before the 7 days end.

## Role restore questions

### 

### 

### 

## Everyone back, every role in place

RestoreCord remaps your members' roles after a restore, so the rebuilt server feels like home again.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
