Why your Discord bot cannot do that: permissions, roles and channel overrides

The three layers

Start with the server-level permissions from every role a member has. Then apply category overrides, then channel overrides. A channel override beats a category override, and both beat the server-level permission — which is why a moderator can be locked out of one channel without losing their role.

Bots are members with roles, so exactly the same rules apply. There is no separate “bot permission” switch.

The role position rule

Discord will not let a bot give, remove or moderate a role that sits above the bot’s own highest role. If Lyx’s role is at the bottom of the list, it cannot hand out your member role even with Manage Roles ticked.

Drag the bot’s role above the roles it manages in Server Settings → Roles. It does not need to be above roles it never touches, and it should not be above the owner.

Least privilege, feature by feature

• Logging: View Channel, Send Messages, Embed Links in the log channel. Nothing server-wide.
• Moderation: Ban Members, Kick Members, Moderate Members, Manage Messages.
• Roles and level rewards: Manage Roles, with the bot role above the roles it gives.
• Tickets: Manage Channels (to create private channels), plus Read Message History.
• Welcome messages: Send Messages and Embed Links in the welcome channel.

Channel overrides that silently block

A private channel that denies View Channel to @everyone also denies it to the bot unless the bot’s role is added. This is the single most common reason a welcome or log message “disappears”.

The same applies to Send Messages: a channel where @everyone is muted will block the bot too. Add the bot’s role to the channel with the permissions it needs, or put the channel under a category the bot can access.

Diagnosing a failure

• Read the error message. Discord names the missing permission; Lyx repeats it in plain words.
• Check the bot’s role position first — it explains most role and moderation failures.
• Check the channel overrides second — it explains most “cannot see” and “cannot post” failures.
• Test in a channel with no overrides. If it works there, the problem is the channel.
• Re-invite the bot only as a last resort: a fresh invite fixes a missing scope, not a role position.

When to use Administrator

Almost never. Administrator bypasses every check, which means a compromised bot can delete channels, roles and messages in seconds. The features people give it for — logging, tickets, role menus — need four or five specific permissions, not all of them.

If you are debugging and Administrator “fixes” it, you have found the missing permission. Remove Administrator afterwards and grant that permission instead.