Discord bot intents explained
Gateway intents control which events Discord sends your bot. Choosing them poorly either breaks features or exposes you to data you do not need.
What intents are
Intents are subscriptions. Without the message content intent, many message-based prefix commands will not see message text. Without guild members intent, member caches and join events may be incomplete. Privileged intents require enabling toggles in the Discord Developer Portal and, at scale, Discord approval.
Least privilege
Enable only intents your features require. A slash-command-only utility bot often needs fewer privileged intents than a logging or anti-raid bot. Fewer intents mean less data to protect and a clearer privacy story for server owners.
Portal vs code mismatch
A common outage pattern: code requests an intent that is disabled in the portal, or the reverse. After changing intents, restart the process and watch the ready/login logs for warnings.
Privacy and trust
If your bot reads message content, document why on your support site. Community admins increasingly ask. Pair technical choices with honest product pages.