> RestoreCord bot card says privileged intents are disabled? Turn on Server Members and Message Content Intent in the Developer Portal, then restart the bot.

Source: https://restorecord.help/privileged-intents-disabled

# Privileged intents are disabled: getting your bot's events back

The bot card in RestoreCord shows a yellow warning about privileged intents. It looks alarming, but it's two switches in the Discord Developer Portal and one restart.

[Open Dashboard → Bots](https://restorecord.com/dashboard)[All setup fixes](https://restorecord.help/)

Short answer

Discord rejected your bot's gateway intents, so RestoreCord restarted it without member and message-content events. In the Developer Portal, open your application's Bot page, switch on Server Members Intent and Message Content Intent, save, then press Restart Bot in Dashboard → Bots.

## What actually happened

Every Discord bot connects to Discord's gateway and asks for the kinds of events it wants to receive. A few of those, called **privileged intents**, only work if the bot's owner has switched them on in the Developer Portal. When a bot asks for one that's switched off, Discord refuses the connection.

RestoreCord doesn't leave your bot dead in the water when that happens. It restarts the bot without the rejected intents and puts **Privileged intents are disabled** on the bot card, so you know exactly why it's running with less than it should.

## The intents that matter

| Intent                 | Needed by RestoreCord | What it delivers                           |
| ---------------------- | --------------------- | ------------------------------------------ |
| Server Members Intent  | Yes                   | Member events in the servers the bot is in |
| Message Content Intent | Yes                   | The content of messages the bot can see    |
| Presence Intent        | Not listed            | Online status and activity of members      |

## Switch them on

1. 1Open the Discord Developer Portal and select the application behind your RestoreCord bot. The client ID on the bot card tells you which one.
2. 2Go to the Bot page and scroll to Privileged Gateway Intents.
3. 3Turn on Server Members Intent and Message Content Intent.
4. 4Click Save Changes in the bar at the bottom. Nothing is stored until you do.
5. 5Return to Dashboard → Bots in RestoreCord and press Restart Bot.

Changing switches in Discord doesn't affect a connection that's already open. The restart is what makes the bot ask again with the new settings, so don't skip it.

## If the switches are greyed out

Discord treats bots in 100 or more servers differently: privileged intents have to be requested and approved through Discord's bot verification process instead of toggled freely. Most RestoreCord bots are custom bots for one community or a small network and never get near that, but if yours does, the approval has to come from Discord before the warning can clear.

## Check the rest of the card while you're there

An intents warning often turns up after someone has been tinkering in the Developer Portal. Look over the other things that live there too:

### Token and client secret

RestoreCord validates both against Discord as you type, and a green ring means they were accepted. If anyone pressed Reset Token or regenerated the secret, paste the new values into the bot's credentials and save before running any server operation.

### Redirect URL

An **Invalid Redirect URL** warning on the same card means the callback is missing from OAuth2 → Redirects. It has its own walkthrough in [fixing an Invalid Redirect URL](https://restorecord.help/invalid-redirect-url).

### Slash commands

You never register commands by hand. RestoreCord loads them automatically once the bot is connected, and the same restart refreshes them if they ever look out of date.

> A good habit: after any change in the Developer Portal, restart the bot and verify once with a spare account. It takes a minute and catches problems before members do.

## Keeping it from coming back

* Use the Add New Bot wizard in the dashboard for new bots. It validates token, secret and redirect URL as you go.
* Keep Developer Portal access to the people who really need it, ideally a dedicated account that owns the application.
* Rotate credentials in a quiet period, then restart and test straight away.

If members are verifying but not getting their role, that's a role order problem, covered in [the role position guide](https://restorecord.help/verified-role-not-given). For anything else, start from [the symptom list on the home page](https://restorecord.help/).

## Turn the intents back on

1. 1  
### Open the Bot page  
In the Discord Developer Portal, pick the application behind your RestoreCord bot and open Bot.
2. 2  
### Enable both intents  
Under Privileged Gateway Intents, switch on Server Members Intent and Message Content Intent.
3. 3  
### Save in Discord  
Confirm the Save Changes bar at the bottom of the page so Discord stores the new switches.
4. 4  
### Restart from RestoreCord  
Back in Dashboard → Bots, press Restart Bot and wait for the green status dot to return.
[Bot management in the RestoreCord docs](https://restorecord.com/docs/guides/bot-management)

## Privileged intent questions

### 

### 

### 

## Bot reconnected with everything it needs

With both intents on and a fresh restart, your RestoreCord bot is back to backing up and protecting every member who verifies.

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