Skip to main content

Discord is asking me to justify Privileged Gateway Intents (10,000 users)

Discord asking you to justify Privileged Gateway Intents after 10,000 users? Learn what it means, which intents to request, how to apply in the Developer Portal, and what to write so member verification, roles, and recovery keep working.

Last updated: August 29, 2026

What this message means

If Discord is asking you to justify Privileged Gateway Intents, your custom Discord app has reached Discord’s review threshold.

As of June 10, 2026, Discord no longer uses the old “100 servers” rule for this. Privileged Intent review is now based on unique users who can see your app across all servers it’s installed in.

Once that number goes over 10,000, Discord requires you to apply and explain why your bot needs those intents.

This is a Discord Developer Portal requirement for the bot application you connected to VaultCord. VaultCord cannot submit or approve this request for you — only the Discord app owner/team can.

Important clarification

This is not the same as “my Discord server has more than 10,000 members.”

Discord counts:

  • Unique users who can access your bot/app

  • Across all servers the bot is in

So a bot in a few large communities can hit the limit even if it isn’t in many servers.

What are Privileged Gateway Intents?

Discord currently has three Privileged Intents:

Intent

What it unlocks

Server Members Intent

Member join/leave/update events and listing members

Message Content Intent

Reading message text, embeds, attachments, components

Presence Intent

Online/offline status, activities, platform info

You should only request intents your bot actually needs.

For most VaultCord setups, Server Members Intent is the one that matters for features like syncing/pulling members and role management. You usually should not request Presence Intent unless you have a clear, required use case. Only request Message Content Intent if your bot truly needs message text to function.

What you should do (step by step)

1. Open your bot in the Discord Developer Portal

  1. Go to Discord Developer Portal

  2. Select the application you use with VaultCord

  3. Open the Bot tab

  4. Scroll to Privileged Gateway Intents

You’ll usually also see a portal alert / button to start the Privileged Intent application.

2. Apply within 90 days

After Discord notifies you, you generally have 90 days to submit.

While your application is under review:

  • Your bot can keep using the intents you’re requesting

  • Your bot can keep joining servers / reaching new users

If you don’t apply in that window, Discord can remove Privileged Intent access. You can still apply later, but features that depend on those intents may stop working until access is restored.

3. Only request what VaultCord needs

In most cases, request:

  • ✅ Server Members Intent — needed for member-list related features (Pull Members, member sync, mass role tools, join-related bot behavior)

  • ❌ Presence Intent — usually not needed for VaultCord verification / backup

  • ⚠️ Message Content Intent — only if you have a real use case that requires reading message content (most VaultCord verification flows do not need this)

Requesting intents you can’t clearly justify can delay or hurt approval.

4. Write a clear justification

Discord rejects vague answers like “my bot needs members.”

Be specific:

  • What feature uses the intent

  • Why that feature can’t work without it

  • How you handle the data responsibly

Example justification for Server Members Intent

This bot provides member verification, role assignment, and community recovery tools for Discord servers.

Server Members Intent is required so the bot can:

  • Receive real-time GUILD_MEMBER_ADD, GUILD_MEMBER_UPDATE, and GUILD_MEMBER_REMOVE events

  • Fetch and sync the full guild member list for verified-role assignment and access control

  • Detect when members leave or lose roles so access can be updated correctly

  • Restore verified members into a server after a raid, nuke, or accidental wipe

Without Server Members Intent, the bot cannot reliably detect joins/leaves or manage verified members at scale. Slash commands and interactions alone are not enough, because these features depend on member list access and member lifecycle events.

Member data is used only for verification, role management, and recovery features requested by the server administrators. We do not use this intent for advertising, scraping, or unrelated data collection. Data is handled securely, retained only as needed for these features, and users can revoke access at any time through Discord’s Authorized Apps settings.

If Discord also asks about Message Content, prefer not requesting it unless you truly need it. If they ask about Presence Intent, usually skip it unless you have a concrete online-status feature.
​

5. After Discord approves access

  1. In Developer Portal → Bot → enable the approved Privileged Intent(s)

  2. Make sure VaultCord is still using that same bot token

  3. Re-check bot permissions in your Discord server:

    • Manage Roles

    • Create Invites

  4. Place the bot’s role above roles it needs to assign

  5. In VaultCord, re-run Pull Members if member sync looks incomplete

Do not give the bot Administrator unless Discord has already verified the app and you fully understand the risk. VaultCord recommends avoiding Administrator for unverified custom bots.

Common questions

“Will VaultCord break if I don’t apply?”

If Discord removes Privileged Intent access and your bot needs those intents, features like Pull Members, member sync, and some role tools can stop working correctly. Apply as soon as you get the notice.

“Can VaultCord submit this for me?”

No. Discord reviews the bot application you own. Only the app owner/team in the Discord Developer Portal can submit the Privileged Intent questionnaire.

“Do I need Discord App Verification too?”

Privileged Intent review and App Verification are separate processes now. Hitting 10,000 users triggers Privileged Intent review. App Verification is a different Discord requirement/process.

“I already had intents approved before. Why am I being asked again?”

Discord now requires annual reapplication for continued Privileged Intent access. When Discord notifies you, reapply within the stated window.

“My request was denied. What now?”

Usually this means:

  • The use case wasn’t specific enough, or

  • You requested an intent you don’t clearly need, or

  • Discord believes an alternative exists

Tighten your answers, only request required intents, and include screenshots/video of Pull Members / role assignment if possible. You can submit again.

Quick checklist

  • Open your VaultCord bot in the Discord Developer Portal

  • Start Privileged Intent review from the Bot page

  • Request only required intents (usually Server Members)

  • Explain VaultCord verification / pull / role recovery clearly

  • Submit within 90 days

  • After approval, enable the intents in the portal

  • Confirm bot permissions + role hierarchy in Discord

  • Re-run Pull Members in VaultCord if needed

Still stuck?

Contact VaultCord Live Chat Support and include:

  • Your Discord Application / Client ID

  • Your VaultCord Server ID

  • A screenshot of the Discord Privileged Intents notice

  • Which intents Discord is asking you to justify

We’ll help you confirm what to request and how to word the use case for your setup.

Related Discord docs

Related Articles
Did this answer your question?