Discord privileged intents

Swipe the table sideways; the application column stays put.

“Scoped use” describes application filtering and channel permissions; the intent itself is app-wide. “Confirm” means the expected workflow still needs app-specific verification.

• Open the bot’s Intents page for its review answers, privacy URL, and proof links for that application only.
• Use the Request column alongside the app-specific evidence and current deployment. Remove unnecessary intents only after the implementation is ready for that change.
• Attach proof from each bot’s Evidence page or the bot’s own #proof section. Do not attach MEE6’s Notion page to a non-MEE6 app.
• If Discord has not asked you to apply, wait. Submit only when Discord’s Developer Portal or email tells you to request privileged intents for that application.

1. Binny Alerts. Review answers

   The analyst writes an ordinary message without mentioning the bot. Binny Alerts creates an editable preview and offers send controls. Reading that original message requires Message Content in the existing workflow; delivering the output does not. Message-context and slash commands remain alternatives to evaluate.

2. Nefarious. Review answers

   The MEE6 Custom Bot setup uses Message Content, Server Members and Presence according to MEE6’s own guide.

3. Enick’s Bot. Review answers

   Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

4. Nefarious Success. Review answers

   Message Content exposes the image and caption that the current bot reads from its configured success channel. The acknowledgement verifies an X repost; it does not demonstrate consent or leaderboard behavior.

5. Wex Alerts. Review answers

   Message Content reads ordinary analyst messages before a branded preview is prepared. Send buttons approve delivery; button interactions alone do not expose the earlier ordinary source message.

6. Wizz Bot. Review answers

   Message Content lets the bot read WizzTrades’ ordinary analyst message and chart attachment before preparing a branded preview. Send buttons approve delivery; the button interaction alone does not provide the earlier ordinary source message. Sending the bot’s own output does not itself require this intent.

7. Qiko Alerts. Review answers

   Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

8. Nefarious News. Review answers

   Outbound news publishing does not require Message Content, Server Members or Presence.

9. Nefarious Alerts. Review answers

   The sticky command reads an administrator’s message text using Message Content. Member-join and role-snapshot features separately require Server Members.

10. Nefarious Backup. Review answers

    Message Content lets the bot serialize ordinary channel history, embeds and supported attachments into its archive and create backup copies. The deployed command check restricts operator controls to configured user IDs.

11. Nefarious Widget. Review answers

    The bot counts occupants of the livestream voice channel and supplies that count to the overlay. It uses Guilds and Voice States only; Message Content, Server Members and Presence are disabled.

12. Nefarious Options Levels. Review answers

    Scheduled publishing needs no privileged intent. The current nl prefix-command feature uses Message Content; a slash-command migration could remove that dependency.

13. Johnny Alerts. Review answers

    Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

14. Drippy Alerts. Review answers

    Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

15. Dizu Alerts. Review answers

    Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

16. Slade Alerts. Review answers

    Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

17. Nefarious Congress Tracker. Review answers

    Outbound public-filing updates do not require any privileged intent.

18. Nefarious Charting. Review answers

    The current prefix-command handler reads message text. Slash commands are a feasible alternative and should be evaluated before requesting Message Content.

19. Nefarious Copytrading. Review answers

    Message Content exposes the CzarFX trade embed returned by Discord REST. The running bot reads that embed, parses pair, side, entry, stop and targets, and passes the signal to its cTrader execution path. Outbound logging alone does not require Message Content.

20. Dingus Alerts. Review answers

    Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

21. Showtime Alerts. Review answers

    Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

22. kly Alerts. Review answers

    Message Content lets the relay read the analyst’s original message and attachments before delivering it to configured channels. Sending the bot’s own output does not itself require that intent.

23. JCACTrades RadioFX (Forex). Review answers

    The operator identifies this application as JCAC’s forex and gold alert relay. Reading ordinary analyst messages for a relay uses Message Content; publishing the bot’s own output alone does not require this intent. The retrieved destination verifies the Forex bot identity and delivered content, while the source-reading runtime has not been inspected.

24. JCACTrades Radio (Crypto). Review answers

    The operator identifies this separate application as JCAC’s crypto alert relay. Reading ordinary analyst messages for a relay uses Message Content; publishing the bot’s own output alone does not require this intent. This retrieved destination verifies the bot identity and delivered content, while the source-reading runtime has not been inspected.

• All three: Nefarious. The MEE6 Custom Bot follows its provider’s feature requirements.
• Server Members and Message Content: Nefarious Alerts. Backup currently has Server Members disabled; its optional full-roster feature would require it.
• Message Content only: Binny Alerts, Enick’s Bot, Nefarious Success, Wex Alerts, Wizz Bot, Qiko Alerts, Nefarious Backup, Nefarious Options Levels, Johnny Alerts, Drippy Alerts, Dizu Alerts, Slade Alerts, Nefarious Charting, Nefarious Copytrading, Dingus Alerts, Showtime Alerts, kly Alerts, JCACTrades RadioFX (Forex), JCACTrades Radio (Crypto).
• No privileged intents: Nefarious News, Nefarious Widget, Nefarious Congress Tracker. Widget uses voice-state events, which are not privileged.