Skip to main content
Restore lets you get your members back if your server gets deleted, nuked or taken over. Members verify once by authorizing a bot, and from then on you can add them to any server you run, even a brand new one. The bot they authorize isn’t mira. It’s a bot you make yourself in the Discord Developer Portal, which we call your restore bot. That way the authorizations belong to you, and you aren’t depending on anyone else’s application staying up. You only do this once. The same restore bot works for every server you set verification up in.

​
Making the bot

Use a fresh application for this. Don’t reuse a bot that already does other things, and don’t use a custom instance token.
  1. Go to the Discord Developer Portal and press New Application. Name it whatever you want your members to see when they authorize, most people just use the server’s name.
  2. Open the Bot tab and press Reset Token, then copy the token somewhere safe for a minute. Discord only shows it once.
  3. Open the OAuth2 tab and press Reset Secret under Client Secret, then copy that too.
  4. Still on the OAuth2 tab, press Add Redirect and paste this in:
    Then hit Save Changes at the bottom. If you forget to save, mira won’t accept the bot.
Getting the bot token and client secret and adding the redirect URL in the Developer Portal
You don’t need to turn on any intents. The restore bot never actually comes online, mira just uses it in the background, so it’ll show as offline in your member list and that’s normal. Leave Requires OAuth2 Code Grant off on the Bot tab. You can turn Public Bot off if you don’t want anyone else adding it to their servers.

​
Connecting it to mira

Pick Restore Bot from the menu and press Connect Bot. A form pops up asking for the bot token and the client secret. Paste them in and submit. The form is private, so nothing ends up in chat. mira checks the token works, that the secret belongs to the same application, and that the redirect URL is saved before it accepts anything. If something’s off it’ll tell you which one. Once it’s connected, press Invite Bot to add it to your server. The invite already has the permissions it needs, mainly Manage Roles so it can hand out your verified role.
Never post your token or client secret anywhere, including screenshots and screen recordings. Anyone with the token controls the bot. If one leaks, reset it in the Developer Portal and connect the bot again with the new one.

​
Keeping it working

If you reset the token, reset the secret or remove the redirect URL, verification in your servers stops working and mira will DM you about it. Fix whatever changed, then press Connect Bot again with the current token and secret. Don’t delete the application. Every member who verified authorized that specific bot, so if it’s gone, those members can’t be pulled anymore. The same goes for switching to a different bot later: you can, but the members who verified with the old one stay tied to it. If you want to stop using restore, press Disconnect on the Restore Bot page. Your pools are kept, but nothing can be pulled until you connect the bot again.

​
Letting someone else pull

You can give up to 10 people access to your member pools, so a co-owner can run a pull if you’re not around. They use your restore bot, they don’t need their own.
You can also pick them from the Restore Bot page. Only you can delete your pools, managers can just view and pull them. Next, set up verification in your server.