> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mira.party/llms.txt
> Use this file to discover all available pages before exploring further.

# Pulling members

> Add the members who verified back into another server.

Every server you set verification up in gets its own **member pool**, named after the server. Pulling takes the members from a pool and adds them to a server you pick. They don't get an invite or have to click anything, they just show up.

Pools stick around even if the server they came from gets deleted, which is the whole point. If your server is gone, make a new one, invite mira, and pull.

## Before you pull

The server you're pulling into needs three things:

* mira has to be in it, and you need Manage Server there.
* Your restore bot has to be in it. The pull page has an **Invite Bot** button for this.
* If you want to give everyone a role when they arrive, your restore bot's role has to be above that role.

## Starting a pull

```javascript theme={null}
!restore pull
```

Press **Start Pull** and it runs in the background. You can close the panel, it keeps going.

## How long it takes

Members get added one at a time, a bit over a second apart, so Discord doesn't get suspicious of your bot. Roughly 2,000 members an hour.

There's a limit of 2,000 members a day for each restore bot. If your pool is bigger than that, the pull waits and picks back up on its own the next day.

You can only run one pull at a time. After a full pull into a server, you'll have to wait a little before pulling the same pool into it again, from 10 minutes up to 2 hours depending on how big the pool is. Only Newly Verified pulls skip that wait.

## Checking on it

Pick **Pull Progress** from the `!restore` menu to see how it's going. It shows how many were added, how many were already in the server, and roughly when it'll finish. You can pause, resume or cancel from there. Cancelling doesn't remove anyone who was already added.

If your restore bot stops working partway through, say the token got reset, the pull pauses itself. Reconnect the bot on the Restore Bot page, then come back and press **Resume**.

A few members not making it is normal:

* **Revoked Access** means they went into their Discord settings and removed your bot from Authorized Apps. You can't pull them anymore until they verify again.
* **At Server Limit** means they're already in 100 servers, which is Discord's cap.

## Looking at a pool

Pick a pool from the `!restore` menu to see how many members can be pulled, how many left on their own, how many revoked access, and when someone last verified.

**Delete Pool** removes it for good and revokes every member's authorization, so they can't be pulled by anyone. There's no undo, so only do this if you really mean it.

## Commands

| Command | Permission | What it does |
| - | - | - |
| `restore` | Manage Server | Opens the restore panel |
| `restore pull [pool]` | Manage Server | Starts a pull, optionally from a named pool |
| `restore log [channel]` | Manage Server | Sets the verification log channel. Alias `logs` |
| `restore allow <user>` | | Lets someone view and pull your pools |
| `restore revoke <user>` | | Takes that access away. Alias `disallow` |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.