Check the application’s verification page
Discord requires verification for an app to grow past 100 servers. Open your application in the Developer Portal and check the App Verification tab for its current requirements.
The checklist is more useful than an old screenshot or a fixed timeline. Complete it before growth makes verification urgent. Discord’s verification guide describes the process, including identity verification for the owner of the team that owns the app.
two separate checks
Verification and privileged intents are different.
Verification allows the app to grow. An intent request asks for access to particular data. Completing one does not mean every requested intent is approved.
Prepare a clear description of the bot
- Explain the main features in plain language, with commands reviewers can try.
- Keep the bot online and make its install flow work in a fresh server.
- Publish an accurate privacy policy and any required terms.
- Provide a support contact that someone on the team checks.
- Review who owns the application and who can access its credentials.
Describe what the bot actually does today. A short explanation with a working example is more useful than a long list of features you plan to build.
Keep identity documents within the verification provider’s flow reached from the official portal. Do not send them through a support-server DM or an unofficial form.
Ask only for the data your features need
Server Members
Presence
Message Content
Follow the eligibility and approval instructions shown for your app. For each request, explain the user-facing feature, why a narrower approach is insufficient, what data you keep, and when it is deleted. See Discord’s intent application guide.
If the application needs more work
Read the specific feedback
Check the portal and official support messages. Fix the missing requirement instead of resubmitting the same explanation.Test with reduced access
Handle unavailable intents without crashing. Tell server staff which feature needs attention and keep unrelated commands working.Keep your information current
Update privacy details, support links, and team access when the bot changes. Revisit data collection when you add features.
Approval does not replace permission checks, reliable hosting, or ongoing policy compliance. Use the permissions guide and safety guide as you prepare the bot for wider use.