The Privileged Intent Overhaul: What Discord's New API Thresholds Mean for Bot Devs

The Privileged Intent Overhaul: What Discord's New API Thresholds Mean for Bot Devs

Your bot does not need to be famous to hit a wall.

Once an app reaches 10,000 users, Discord wants a review before it keeps its most sensitive gateway access. And for apps that already passed review, that access now expires unless you reapply every year.

This article explains the Discord Privileged Intents change: who it affects, how the 90 day window works, and what to do before a notification lands in your inbox.

🔥 Main Story: Discord Privileged Intents Now Depend on a 10,000 User Threshold

Discord's developer support team announced the change in its Privileged Intent access article. It covers the Guild Members, Presence and Message Content intents.

The review threshold is now based on users, not servers. Apps under 10,000 users can keep using the Developer Portal toggle.

The key fact: Discord says the data each intent provides has not changed. Only the rules for when access requires review did.

🎮 What Happened

Before the change, apps in fewer than 100 servers could switch Privileged Intents on themselves. Apps in 100 or more servers had to apply, and could be blocked from joining new servers until review finished.

Discord's support article is dated June 11, 2026, and BondBot's explainer puts the switch at June 10. Discord says apps with existing approvals should expect a reapply notice between the announcement and the end of 2026, so many developers may be seeing them now.

🧭 Navigation: Main Story → What Happened → Why It Matters → Key Details → Deeper Breakdown → Comparison → Creator Note → What Happens Next

🔄 Review flow: 📈 App grows → 🔔 Notice at 10,000 users → 📝 Apply within 90 days → 🔍 Discord reviews → 🔁 Reapply each year

🧠 Why It Matters

These three intents power a lot of everyday bot features. Moderation, logging, welcome flows and member tracking often depend on them.

Losing access can break a bot quickly. Discord's stated reason for the annual check is that a bot's purpose can drift over time.

⚠️ Important: Under the new rules, apps over the threshold keep working while they wait. Discord says new server installs are not blocked during review.

⚡ Key Details

🔍 Deeper Breakdown

How Discord Counts Users

Discord counts unique users who have access to your app across every server it is installed in. The app or team owner is notified when the 10,000 mark is reached.

Discord also says it does not show your user count in the Developer Portal. Third party docs add a practical point for custom bots. Invite Tracker's guide says a bot living in one server with 10,000 or more members is covered too.

The 90 Day Window and Annual Review

When the notice arrives, you have 90 days to apply. If you apply inside that window, your app keeps its intents while Discord reviews the submission.

If you miss the window, access is removed, though you can apply again at any time. Approved apps get the same 90 days after each yearly reapply notice, and the form asks about your app's current functionality, your use case for each intent, and your data practices.

If a request is denied, Discord sends a notice. Sometimes you get extra time to fix issues, and in other cases access is removed.

Do You Actually Need the Intent?

Discord pushes developers to check before applying. Its guide, You Might Not Need a Privileged Intent, walks through alternatives for each intent.

The headline example is prefix commands. Bots that read message content for them can move to application commands and drop the Message Content intent entirely.

💡 Note: Discord's review guide suggests writing your answers so they are easy to update, since you will reapply every year.

What We Know

• Confirmed: the threshold is 10,000 unique users, you have 90 days to apply, approved apps must reapply annually, and apps under the threshold are unaffected.
• Reported: custom bots in a single large server count, and some third party bots warn that losing intents would break most features.
• Not confirmed: how long reviews take, and how strict reviewers will be on the annual check.

What Could Happen Next

This section is speculation. Discord could surface user counts in the Developer Portal, since developers currently cannot see the number that triggers review.

It could also publish review timelines or guidance on common denials. None of that has been announced.

📊 Quick Comparison

💡 Creator Note

For bot developers and community owners running custom bots, preparation beats panic. Here is a short list to work through.

• Audit which intents your bot uses and why.
• Move prefix commands to application commands where you can.
• Watch your email, system DMs and the Developer Portal for notices.
• Keep a short written record of your use case and data practices for each intent.

🚨 What Happens Next

• Watch for reapply notices through the end of 2026.
• Watch your Developer Portal for the threshold alert.
• Watch Discord's docs for new alternatives to Privileged Intents.
• Watch for updates to the review form and guidance.

Notice arrives → Audit intents → Submit within 90 days → Keep access → Reapply next year

Final Takeaway

This is a bigger change than the headline number suggests. The shift from servers to users makes the threshold fairer for niche bots, but it also catches single server bots with large communities.

The annual reapply is the part developers should plan around. Access is now something you maintain, not something you win once.

The safest bot is the one that only asks for the intents it can explain in a sentence.

🔗 Sources

1. Changes to Privileged Intent Access for Discord Apps: Discord's official announcement, including counting rules, the 90 day window and annual review.
2. Getting Started with Privileged Intent Review: Discord's developer guide to applying and preparing for annual review.
3. You Might Not Need a Privileged Intent: Discord's guide to alternatives for each intent.
4. What Are Privileged Intents?: Discord's explainer on what each intent does.
5. BondBot on AI bots and message reading: Third party explainer with the June 10 switch date and mechanics.
6. Invite Tracker custom bot intent review: Third party guide on how the threshold applies to single server custom bots.
7. MEE6 guide to the Privileged Intents form: Third party walkthrough of the application form.