What Permissions Does AdviceBot Need?

2 min czytaniaZaktualizowano 12 października 2026

AdviceBot needs permissions to send messages, assign roles, manage tickets, and perform the moderation actions you enable.

What Permissions Does AdviceBot Need?

AdviceBot needs permissions to send messages, assign roles, manage tickets, and perform the moderation actions you enable.

Its default invite requests Administrator access. If you change that access, the permissions it needs depend on the features you use.

Default Bot Permissions

Administrator grants all Discord permissions and bypasses channel permission restrictions. However, role hierarchy still limits which roles and members AdviceBot can manage. See Discord’s permission documentation for details.

You can check the bot’s permissions under Server Settings → Roles → AdviceBot → Permissions.

Permissions for Individual Features

If you configure permissions manually, these are common permissions to check:

  • View Channel — access the channels used by your modules.
  • Send Messages — send welcome messages, notifications, and panels.
  • Embed Links — send messages containing embeds.
  • Attach Files — upload images and files.
  • Read Message History — access previous channel messages.
  • Add Reactions — add reactions to reaction-role panels.
  • Manage Roles — assign and remove self-roles, verification roles, and level rewards.
  • Manage Channels — create and manage ticket channels.
  • Manage Messages — delete messages when a moderation feature requires it.
  • Kick Members, Ban Members, and Moderate Members — perform the corresponding moderation actions.
  • View Audit Log — identify who performed actions recorded in server logs.

These permissions cover common actions; your enabled modules determine the full requirements. Refer to Discord’s permission definitions and check any warnings in the AdviceBot dashboard.

Role Hierarchy Matters

AdviceBot’s highest role must be above the roles it needs to assign or manage. For kicks and bans, its highest role must also be above the target member’s highest role. Administrator doesn’t remove these restrictions. These rules are explained in Discord’s permission hierarchy documentation.

To adjust the order:

  1. 1Open Server Settings → Roles.
  2. 2Find AdviceBot’s role.
  3. 3Move it above the roles used by your configured features.
  4. 4Save your changes.

For example, if verification assigns a Verified role, place AdviceBot’s role above Verified.

Channel Permissions

If AdviceBot doesn’t have Administrator, check permissions on each channel it uses, including any permissions inherited from its category.

Start with your welcome, notification, log, and panel channels. The dashboard may show warnings when AdviceBot lacks access.

Your Dashboard Permissions

Your account’s permissions are separate from the bot’s permissions:

  • To add AdviceBot, you must own the server or have Manage Server permission.
  • To configure AdviceBot through the dashboard, your account needs Administrator permission.

Discord explains the invitation requirement in its guide to adding apps.

Still Having Trouble?

Check the bot’s permissions, its role position, and any dashboard warnings. Confirm that the affected module is enabled and its settings are saved.

If the problem continues, contact support through the AdviceBot website. Include your server ID, the affected feature, and the exact error message.

Nie znalazłeś odpowiedzi?

Napisz do nas na serwerze wsparcia - zespół pomoże Ci krok po kroku.

Serwer wsparcia
What Permissions Does AdviceBot Need? – Baza wiedzy – AdviceBot