Server security
How to Review Discord Bot Permissions Before Installing an App
A least-privilege approval workflow for Discord owners, admins, and community operations teams evaluating an app for a production server.
The short answer
Before installing a Discord app, name the feature you need and match every requested bot permission to that feature. Do not grant Administrator as a setup shortcut. After installation, inspect the app's Data Access, restrict commands by role and channel, place its bot role only as high as the approved work requires, and test one scoped workflow.
Discord separates bot permissions, app data access, command access, role hierarchy, and channel overwrites. Approving the installation prompt is therefore the beginning of the review, not the end. Discord's current app moderation guide documents the controls server owners can use before and after an app is added.
Review four separate Discord app access layers
A useful approval record names all four surfaces. Looking only at the bot role misses command exposure and data access; looking only at the install prompt misses the channel-specific result.
| Access surface | Where to review | What it controls | Approval question |
|---|---|---|---|
| Install authorization | The app installation flow | The bot permissions requested for the server | Does every requested permission support a feature we will use? |
| Data Access | The installed bot's server profile | What server data the app can access through Discord | Does the developer explain how this data is used and retained? |
| Command Permissions | Server Settings, then Integrations | Which roles, members, and channels can use the app or command | Who should be able to trigger each operational action? |
| Bot role and channel overwrites | Server Settings, Roles, and each relevant channel | What the bot can do and where it can do it | Is its role only as high and its channel access only as broad as needed? |
Discord says an app's visible Data Access can change over time and recommends reviewing the bot profile regularly. In June 2026, Discord also announced stronger recurring review requirements for apps that access message content, member lists, or presence at scale. That platform review is useful, but server owners still decide whether an app's access fits their own community. See Discord's current app data-access update.
What to check before installing a Discord bot
- 1
Name the operational outcome
Write down the feature you are approving, such as meeting transcription, role assignment, audit-log review, or replies in a support channel. A permission without a named outcome is difficult to justify later.
- 2
Map each requested permission to that outcome
Ask what breaks if you remove one permission. Features that only post replies should not inherit moderation or server-management powers merely because the app supports those features elsewhere.
- 3
Escalate Administrator requests
Discord documents Administrator as granting every permission and bypassing channel restrictions. Require a specific explanation, an accountable owner, and an accepted risk before approving it.
- 4
Review the developer and data terms
Read the app profile, privacy policy, retention terms, and support path. Discord's permission prompt describes platform access; it does not replace the developer's explanation of processing and storage.
- 5
Confirm who can approve apps
Discord says members with Manage Server can add apps. Keep that permission with operators who are expected to evaluate app access, not every person who performs routine moderation.
- 6
Define the first test and rollback
Choose one controlled channel, role, or workflow for validation. Record how to disable commands, remove the app, or revoke a permission if the result exceeds the approved scope.
Match Discord permissions to the feature being approved
These are review examples, not a universal install preset. The same app can need a different permission set depending on which features your server enables. Discord's server and channel management reference documents the individual permissions commonly used by app operations.
| Feature | Permissions commonly relevant | Review question |
|---|---|---|
| Post a requested response | View Channel and Send Messages; Read Message History only when prior messages are part of the feature | Which channels need the bot, and can the feature work through a command without broad history access? |
| Join a voice channel | View Channel, Connect, and Speak when the app needs to transmit audio | Which voice or Stage channels are approved, and how are participants notified? |
| Create or edit channels | Manage Channels | Does the app create one scoped channel, or can it alter the wider server structure? |
| Assign or remove member roles | Manage Roles plus a bot role above only the target roles | Which roles may the bot manage, and is it positioned below staff and Administrator roles? |
| Summarize native audit entries | View Audit Log | Does the feature need read access only, without Manage Server or Administrator? |
| Perform moderation | The specific Kick Members, Ban Members, or Moderate Members permission used by the workflow | Can each action be limited to trusted operators and the exact moderation capability? |
Administrator is not another item in that feature matrix. Discord defines it as granting all permissions and bypassing channel restrictions. If a developer recommends Administrator only to reduce setup support, ask for the individual permission list instead.
Lock down the Discord app immediately after installation
Discord's Command Permissions guide says commands from a server-installed app are available to every member in every channel by default unless the developer set default member permissions. Do not wait for misuse before restricting an operational command.
- 1
Inspect the created bot role
Open Server Settings and Roles. Confirm the granted permissions match the approved list and that no one added Administrator during troubleshooting.
- 2
Set the narrowest useful role position
A bot that manages roles needs its highest role above the roles it is allowed to manage. It does not need to sit above owners, administrators, or unrelated staff roles.
- 3
Restrict commands
On Discord desktop, open Server Settings, select Integrations, choose the app, and limit its command audience and channels. Discord does not currently expose these Command Permissions controls on mobile. Review sensitive commands individually instead of assuming the app-wide default is safe.
- 4
Inspect Data Access
Open the bot's profile inside the server and select Data Access. Compare the visible access with the approved purpose and the developer's privacy policy.
- 5
Check channel-specific access
Review the channels where the app will work. A server-level permission may still be restricted by a channel overwrite, while an explicit channel allow can widen access unexpectedly.
- 6
Run one controlled test
Use a non-sensitive channel and a representative operator role. Confirm the intended task completes, unauthorized users cannot trigger it, and failure messages do not encourage blanket permission grants.
After the first test, perform the broader current-state review in the Discord permissions audit checklist. That guide owns the server-wide audit workflow; this guide owns the app approval and initial lockdown decision.
Role hierarchy and channel permissions solve different problems
Moving a bot role higher does not grant general access. Discord separately calculates channel permissions and enforces hidden hierarchy restrictions for actions that affect roles or members.
Role hierarchy controls
- Which lower roles a bot can grant, edit, or sort.
- Which lower-ranked members it can moderate.
- Whether Manage Roles can reach the intended target.
Channel permissions control
- Which text, voice, Stage, or forum channels it can see.
- Where it can send messages, connect, or speak.
- How role and member overwrites change the server base.
Discord's developer permission reference says a bot can grant, edit, or sort only roles lower than its highest role and can grant only permissions it already has. It also states that role position does not generally resolve channel-permission conflicts. Review the official hierarchy and overwrite rules before moving an app above trusted staff roles.
If your task is to restrict a bot or person to one operational space, use the private Discord channel guide for the native member, role, category, and verification workflow.
Keep a small approval record for every production app
The goal is not paperwork for its own sake. A short record lets a new admin understand why an app exists and remove access that no longer has an owner.
Record these fields
- App and developer
- Named operational purpose
- Accountable server owner
- Approved bot permissions
- Observed Data Access
- Allowed commands and channels
- Highest approved role position
- Removal and review trigger
Review the record after enabling a new feature, changing staff or roles, moving channels, receiving a security notice, or seeing a material Discord permission-interface change. A recurring review schedule should reflect the app's impact and data sensitivity.
How Shero applies the same least-privilege standard
Shero's public install requests one audited full-feature set of individual permissions for its AI, moderation, partnership, channel, attachment, and meeting capabilities. It is not a feature-specific install, but it does not request Discord's blanket Administrator permission. Review the complete list in Discord before approving it. If your server will use only a subset of Shero, you can remove unused permissions from Shero's role after installation; the affected features will remain unavailable until their required permissions are restored. The requester's permissions, Shero's bot role, and target-channel permissions still determine whether a supported operation can complete.
Free current-state check
Run Shero's private, read-only server health preview
A server owner or member with Manage Server can run /server-health to review selected high-impact role risks, channels where @everyone can post, server safeguards, and missing Shero capability permissions. The free preview returns the top three risky role findings and priority actions without changing roles, channels, safeguards, or bot permissions.
This is not a certification of every installed app. Shero does not determine whether another developer's data use is appropriate, and the health preview does not automatically rewrite app roles or channel access.
For natural-language server work, the Shero AI assistant page explains the requester checks, bot-role checks, supported tools, and clear failure boundaries used during operations.
Common Discord bot permission questions
Should I give a Discord bot Administrator?
Usually not. Administrator grants every permission and bypasses channel restrictions. Ask the developer which active feature needs each individual permission and approve only that set. If an app cannot explain why it needs Administrator, do not use blanket access as a setup shortcut.
What can a Discord bot see without explicit permissions?
Discord says apps have baseline access to items such as basic member profiles, member roles, message metadata, voice-channel metadata, reactions, and language information. Open the installed bot's profile and review Data Access, then read the developer's privacy policy to understand how the app uses and retains data.
Are Discord app commands available to everyone by default?
Discord says commands from a server-installed app are available to every member in every channel by default unless the developer configured default member permissions. Server admins can restrict an app, channel, role, member, or individual command in Server Settings under Integrations.
Does moving a bot role higher give it channel access?
No. Role position controls which lower roles and members a bot can manage for hierarchy-sensitive actions. Channel access is calculated from server permissions and channel overwrites. Review both surfaces instead of treating a higher bot role as a general permission fix.
How do I check a Discord bot's permissions after installing it?
Open Server Settings, select Roles, and inspect the app's bot role. On desktop, open Server Settings, select Integrations, choose the app, and review command access. Open the bot's server profile and select Data Access, and check any channel-specific overwrites where the app operates.
Can Shero audit every installed Discord app?
No. Shero's private, read-only server-health check reports selected high-impact role risks, open-channel findings, safeguards, and missing Shero capability permissions. It does not certify another app's purpose, privacy practices, or complete data access, and it does not automatically change roles or channels.
Primary Discord sources
This guide was last verified July 11, 2026 against Discord's current public product and developer documentation. Shero product claims were checked against the deployed permission-audit and AI workflow descriptions.
Approve the scope, then prove the workflow
Add Shero without granting Administrator
Review the individual permissions in Discord's install flow, then run the private /server-health preview before deciding whether a complete Supporter report is useful.