English
日本語English简体中文暂无翻译，前往中文首页EspañolSin traducción: ir al inicio en español

If this page is not translated, the link opens that language’s home page.

Discord

Add a Discord Bot or App: Check the Destination and Requested Permissions

For desktop/browser users who want to add a bot/app, cannot see the intended server in the picker or need to check what was installed.

Edited by Gemnao Editorial Team (Japanese)Last checked 2026-10-18
Saved articles →
No account needed. Saved only in this browser.

The short answer

Open Server Settings → App Directory, inspect the app/provider and choose the intended destination. Read requested access before authorizing. Verify server installation in Members and Integrations; an account-added app instead appears in Authorized Apps.

Different symptom or still not fixed? Find the next check →

Key facts

Who can add a server app?
The server owner or a member with Manage Server
Check the destination
An account install and a server install have different scopes
After adding
Verify registration and the provider’s available commands

Find your symptom

Start with your symptom. Skip steps that do not apply to your setup.

What you seeWhat to checkGo to
The intended server is absent from the pickerVerify account, destination and Manage Server permission.Step 1
Unsure which app or permissions to authorizeRead its provider, purpose and requested access.Step 2
Authorization finished, but commands are missingInspect registration before repeating authorization.Step 3

Fixes, in order

Continue this issue

Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.

Step 1｜Check server-management permission and destination

Server app installation requires ownership or Manage Server, not merely membership.

Time: Compare one change at a time

  1. Open the Discord server where you intend to add the app.
  2. Select the server name and open Server Settings.
  3. Confirm ownership or whether your role has Manage Server. Ask the owner if you cannot inspect the relevant setting.
  4. In any installation picker, verify the server name and icon before continuing so another server is not selected inadvertently.

If you lack permission, ask the owner or administrator to evaluate the addition. Do not try to bypass their server controls.

Results that did not fix the problem help the next reader too.

Step 2｜Choose the app through the App Directory

The desktop/browser directory presents the app’s overview and provider information.

Time: Compare one change at a time

  1. Open Server Settings → App Directory.
  2. Search for the required app name or function.
  3. Read its overview, provider, support destination and required access. Directory presence alone does not make every requested permission appropriate to your purpose.
  4. Select Add App and inspect whether the flow proposes adding it to your account or to a server.
  5. Authorize only when the intended destination and requested permissions match the function you want. Cancel if the scope is unclear or excessive.

Administrator is broad access. Do not grant it routinely to make a bot work; require a clear need for the intended function and reject unexplained excess permissions.

Results that did not fix the problem help the next reader too.

Step 3｜Verify registration and available commands

A server-added app appears as a member and under Server Settings → Integrations → Bots and Apps.

Time: Compare one change at a time

  1. Look for the intended bot in the server’s Members list.
  2. Open Server Settings → Integrations and inspect its app entry. For an account installation instead, inspect User Settings → Authorized Apps.
  3. In an appropriate text channel, type / to open the command picker without submitting a command.
  4. Check whether the intended provider’s commands appear; identical command names can belong to different apps.
  5. If missing, use the bot-not-responding guide to compare permissions and channel settings. Inspect registration and provider guidance before deleting or repeatedly reauthorizing.

Results that did not fix the problem help the next reader too.

Avoid

  • Do not authorize a different server/account destination by habit.
  • Do not grant Administrator automatically or run destructive commands merely to test installation.

Important cautions

  • If the server is absent, verify Manage Server and the signed-in account. If authorization completed but registration is unclear, inspect Members/Integrations and the provider’s support before retrying.
  • The walkthrough describes installation choices; this article does not install or authorize an app for you.

FAQ

Do I need Administrator to add a bot?

The server owner or a member with Manage Server can add a server app. The bot’s own required permissions are a separate, feature-specific decision.

Can I add one from a phone?

This walkthrough uses the desktop/browser App Directory. For a mobile-specific route, consult that app’s provider. Use the PC controls when available to inspect the full destination and permission request.

Is a bot different from a Discord app?

Discord uses apps as a broader term for third-party features. Some expose bot commands; others include Activities used in calls or chats.

Sources

English adaptation of the existing Japanese article. Official documentation supports the described controls and limits; comparison sequences are editorial guidance rather than measured results. Follow the permissions of the actual device, account and server, record original settings and verify the outcome before making another change.

Discord: using, adding and removing appsDiscord developer documentation: permissions and role hierarchyDiscordJapanese version of this page