Applying for Discord Privileged Intents
Your bot runs Heimdall on Bifröst's infrastructure, so the hard part - the data handling - is already done. This guide gives you every answer Discord's intent form asks for, copy-paste ready and personalised with your bot's name.
The copy buttons unlock once you enter a name, so you never paste a placeholder. Saved in this browser only.
Do you even need to apply?
You don't have to count members or guess. Discord sends an official DM to the account that owns the bot's Discord application (the token owner) the moment it crosses 10,000 unique reachable users. No DM, no action - just toggle the intents ON in the Bot tab and carry on.
“Your app (YourBot) has reached 10,000 users… your app's access to privileged intents now requires review.” It names a hard Submit by date - you get 90 days from that message. The bot keeps working in the meantime; miss the date and the privileged intents are switched off.
Since 10 June 2026 the trigger is 10,000 unique reachable users (no longer a 100-server count), and App Verification is now separate from intent review. A whitelabel bot is capped at 3 guilds, but a few large guilds can still cross 10,000 - so it's the DM, not the guild count, that tells you.
Which intents to request
Application details
YourBot runs Heimdall, an all-in-one Discord community-management platform operated by Bifröst Development Ltd. It provides moderation and automod, support tickets and modmail, message and audit logging, message translation, Minecraft account linking with whitelist/role sync, Tebex store lookups, and a real-time web dashboard with role-based permissions. Server administrators enable and configure each feature for their own server. The Heimdall platform is documented at https://bifrost.gg/heimdall.
YourBot runs on the Heimdall platform operated by Bifröst; its Privacy Policy is published publicly at https://bifrost.gg/privacy and linked from the footer of every page on our website (bifrost.gg). The policy explicitly covers branded bot instances operated by Bifröst. It is also referenced from our Terms of Service at https://bifrost.gg/terms.
Server Members Intent
YourBot runs Heimdall; its permission system gates every staff action - on both the bot and the web dashboard - on a member's roles (tri-state Allow/Deny/Inherit), which requires member objects and role data. The intent is also used for moderation (role/hierarchy checks and member lookups for warn/mute/ban/kick and the mod log), join/leave handling (welcome messages, autoroles, join-leave logging), member-count gating, and Minecraft integration that syncs Discord roles with Minecraft whitelist/group state.
Message Content Intent
YourBot runs Heimdall; message content is read to power features each server's admins opt into: modmail (relaying messages between a user's DMs and the staff thread), tickets (generating conversation transcripts for the server operator), automod (scanning content against the server's configured word/pattern/spam rules), moderation logging (showing what a deleted or edited message said, via a temporary cache held up to 14 days), translation (translating messages on request via DeepL), and optional AI assistance when a server enables it.
Screenshots to capture
Each intent needs links to screenshots or a short video showing the use case working. Capture them in your own bot's server (not a Heimdall-branded one), then host on imgur or paste a Discord CDN link.
- Dashboard permissions page (Allow / Deny / Inherit)
- A mod action referencing a member's roles
- A welcome message or autorole on join
- Minecraft role-sync settings
- A ticket transcript
- A modmail relay (DM ↔ staff thread)
- Automod catching a message + the infraction
- A message log of a deleted message
- A translation
Acknowledgement & submit
Tick the certification box. It covers apps "owned or operated by an entity" - Bifröst Development Ltd operates your bot, so you have authority to certify on its behalf. Then submit.
Every answer here is true because your bot runs the same Heimdall software on the same encrypted infrastructure. If you operate the underlying Discord application yourself, you are a data controller for your server and Bifröst is your processor; if Bifröst owns it too, Bifröst is the controller. Either way the handling is exactly as described.
