Discord error 4014: Disallowed intent(s)

Your Identify payload requested a privileged intent that your application is not allowed to use, and Discord refused the connection. There are three privileged intents: GUILD_MEMBERS (Server Members, 1 << 1), GUILD_PRESENCES (Presence, 1 << 8) and MESSAGE_CONTENT (Message Content, 1 << 15). Unlike the rest, these must be explicitly switched on per application in the Developer Portal: open your application, go to the Bot page, scroll to Privileged Gateway Intents, and toggle the ones you need. Requesting any of them in code while the toggle is off produces 4014 every time. The code is not reconnectable; reconnect loops only rack up failed identifies.

The rule has a second tier. Apps with fewer than 10,000 users can enable privileged intents freely with the toggles. Once an app exceeds 10,000 unique users across its servers, it must go through verification and be approved for each privileged intent with a use-case justification; the toggle alone is no longer enough, and an unapproved intent also yields 4014. (Older guides talk about a 100-server threshold; the current docs phrase it in users, so check the Developer Portal for what applies to your app.)

The Message Content intent is the one that bites most. Without it, message events still arrive, but content, embeds, attachments and components are empty unless the bot is mentioned, the message is a DM, or the bot authored it. Many bots therefore look "online but silent" rather than crashing; the ones that crash are those that request the intent without enabling it.

While an approval is pending, do not leave the intent in the Identify payload: every failed connect consumes a session start from your daily session_start_limit budget (1,000 identifies per day for most bots), and a supervisor that restarts the process on failure will burn through it and lock the bot out entirely. Ship without the privileged intent, or gate the feature that needs it, until the toggle or the approval is in place. If the toggle looks enabled and 4014 persists, you are almost always looking at the wrong application: compare the application ID on the portal page against GET /oauth2/applications/@me for the token you deploy.

// WebSocket close frame
code: 4014
reason: "Disallowed intent(s)."

// discord.js
Error [DisallowedIntents]: Privileged intent provided is not enabled or whitelisted.

// discord.py
discord.errors.PrivilegedIntentsRequired: Shard ID None is requesting privileged intents that have not been explicitly enabled in the developer portal...

Request the minimum intents. Use slash commands and interactions instead of reading message content where you can; they deliver user input without the Message Content intent. Document which privileged intents your bot needs and why, keep the Developer Portal toggles in your deployment checklist, and plan the verification and intent approval process as you approach the threshold. The full walkthrough is in Discord bot not responding.

The three privileged-intent rows, the review threshold and the identify budget are collected on the Discord limits page.