> Keep the custom bot behind RestoreCord healthy: a dedicated owner, both privileged intents, safe token rotation, correct role order and what Delete Bot removes.

Source: https://restorecord.website/restorecord-bot-hygiene

# Keeping the bot behind your RestoreCord server healthy

Every RestoreCord server runs on a custom Discord bot you own. Look after it and verification and recovery just work. Neglect it and the day you need a pull is the day you find out.

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

Short answer

Give the bot a dedicated owner, use it only for RestoreCord, enable Server Members and Message Content intents, keep its role above the roles it manages, and update credentials in the dashboard straight after any change in the Developer Portal.

## Why the bot matters so much

Your members approve **your bot** when they verify, not a shared RestoreCord one. That's what lets the bot carry your name and avatar, and it's also why the bot's health decides whether you can pull those members later. Five habits keep it in shape.

## 1\. Don't let a personal account own it

If the Discord application lives under one person's everyday account, that account becomes a single point of failure. Put it under a dedicated owner account or a Developer Portal team that the people running the server control together.

## 2\. Give it one job

It's tempting to bolt giveaways or experimental commands onto a bot that's already in the server. Don't. A bot reserved for verification and recovery has fewer moving parts and less exposure. Run your other automation on a separate bot.

## 3\. Keep both privileged intents on

If the bot card in **Dashboard → Bots** says `Privileged intents are disabled`, Discord rejected them and the bot restarted without member and message-content events. Fix it in the Developer Portal:

1. 1Open your application in the Discord Developer Portal and go to the Bot page.
2. 2Turn on **Server Members Intent** and **Message Content Intent** and save.
3. 3Back in RestoreCord, use **Restart Bot** so it reconnects with the new settings.
4. 4Watch for the green status dot on the bot card.

## 4\. Treat credentials as a pair of keys

RestoreCord checks the token and client secret against Discord as you type them, and a green ring means Discord accepted them. Regenerate either one in the Developer Portal and the old value stops working, so paste the new one into the Credentials card and save before you run anything else. Rotate during a quiet hour, then verify once with a staff account.

### Bot Credentials

Sensitive information used to authenticate your bot

Bot Token

••••••••••••••••••••••••••••••••

Client Secret

••••••••••••••••••••••••

Valid Redirect URL

An "Invalid Redirect URL" warning means the callback on the bot card is missing from your application's OAuth2 settings. On a custom domain, the callback follows this pattern:

Callback on a custom domain

```
https://verify.example.com/api/callback
```

Moving to a new domain? Add the new callback in Discord first and leave the old one in place until the new domain is active and tested, or live verification links break mid-switch.

## 5\. Keep the bot role on top

Discord won't let a bot manage a role above its own highest role. In Server Settings → Roles, drag the bot's role above the verified or unverified role RestoreCord gives or removes, then refresh the dashboard. Do the same after creating any new role the bot needs to hand out.

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

Verified

Member

RestoreCord

BOT

Move RestoreCord above Verified

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

## Before you press Delete

| Action      | What actually happens                                                                                    |
| ----------- | -------------------------------------------------------------------------------------------------------- |
| Restart Bot | Reconnects to Discord. Safe, and the right move after intent or credential changes.                      |
| Delete Bot  | Removes the bot and every member and server record attached to it. Blocked while a server still uses it. |

Deleting cannot be undone, so check the attached servers first. If members are struggling at the verify step rather than the bot itself, see [the two common verification errors](https://restorecord.website/verification-error-fixes). More on RestoreCord's full toolkit is on the [home page](https://restorecord.website/).

## A quick bot health routine

1. 1  
### Give the bot its own owner  
Put the Discord application under a dedicated owner or Developer Portal team rather than a personal account.
2. 2  
### Turn on both intents  
Enable Server Members Intent and Message Content Intent in the Developer Portal, then restart the bot from the dashboard.
3. 3  
### Lift the bot role  
Drag the bot's role above the verified or unverified role it manages in Server Settings → Roles.
4. 4  
### Test with a staff account  
After any credential or domain change, verify once with a second account to confirm the flow still works.

## Custom bot care questions

### 

### 

### 

## Your bot, kept online for you

Connect your own Discord application and RestoreCord keeps it running 24/7, on every plan including Free.

[Connect your bot](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
