Levlix Bot Permissions

Levlix can only do what Discord allows it to do. When a role or a channel withholds a permission, the feature stays switched on and quietly does nothing.

Why Permissions Matter

Discord does not warn you when a bot is missing something. It refuses the action, returns a permission error that only reaches the bot's own log, and nothing appears in your server. From the outside that looks like a feature which broke for no reason:

• A member joins and the welcome message never arrives, because Levlix may not post in the welcome channel.
• A log channel stays empty for days, although logging is switched on.
• A level role is never handed out, although the reward is configured.

How Discord Decides What Levlix May Do

Levlix is a normal member of your server. Discord works out what it may do in a given channel from three places.

Roles

Every role Levlix holds contributes its permissions, and the result is the sum of all of them. There is no separate bot permission: if Levlix holds three roles, a permission granted on any one of them counts as granted for the whole server.

Channel Overrides

Every channel can allow or deny a permission for a role or for a single member. An override beats the server wide setting. A role may carry Send Messages everywhere on the server and still be denied it in one channel, and that denial wins.

Categories

A channel inherits the overrides of its category as long as it has none of its own. Deny the Levlix role something on a category and every channel below it is affected, which is the most common reason a whole section of the server goes silent at once.

Checking What Levlix Has Right Now

Server Wide

1. Open Server Settings, then Roles.
2. Select the Levlix role, the role Discord created when the bot joined.
3. Read through the permission list. This is what Levlix may do everywhere, unless a channel says otherwise.

In a Single Channel

1. Open the channel settings and switch to the Permissions tab.
2. Look for the Levlix role or for the bot as a member. If neither is listed, only the category and the server wide roles apply.
3. Discord can also show you the result for one channel. In the permission view of the channel, pick the Levlix role or the Levlix member and Discord lists the permissions that actually apply there, including everything inherited from the category. That view is the fastest answer to "may Levlix post here".

Granting a Missing Permission

For the Whole Server

1. Go to Server Settings, Roles, Levlix.
2. Switch the permission on and save.

If Levlix holds several roles, granting the permission on any one of them is enough.

For One Channel

1. Open the channel settings and switch to the Permissions tab.
2. Add the Levlix role or the Levlix member if it is not listed yet.
3. Set the permission to the green check mark. The grey slash in the middle means the channel takes the setting from the role or the category, and the red cross denies it here even when the role grants it.

Private Channels

A channel that is hidden from @everyone needs one permission more: View Channel. Without it Levlix does not see the channel at all, cannot post in it, and the channel does not even appear in the channel pickers of the dashboard. Grant View Channel and Send Messages to the Levlix role directly in that channel.

The Minimum for Every Channel Levlix Posts In

Role Hierarchy

Permissions are only half of the story. Discord also compares positions. Levlix can create, assign and remove only those roles that sit below its own highest role, and it cannot moderate a member whose highest role sits above its own. So Manage Roles is granted and the level role is still not handed out, or timeouts keep failing on your moderators. In both cases the target simply sits too high. The server owner can never be moderated by a bot, whatever the hierarchy looks like.

What Each Module Needs

A module only needs its permissions once you switch it on. The table lists what Levlix asks for and why.

Auto-moderation asks for more once you go further: escalation additionally needs Kick Members and Ban Members, and raid lockdown additionally needs Manage Roles. Both are only required once you switch that specific option on.

Anti-nuke without View Audit Log receives nothing at all and silently never fires. What the response itself needs depends on the action you configured, which is Ban Members, Kick Members or Manage Roles.

What the Dashboard Shows

You do not have to walk through every channel by hand. The Levlix dashboard marks a channel on the settings pages when Levlix cannot post in it, so you can see before saving that the message would never arrive. On the module page a warning appears as soon as an enabled module is missing a permission, and it names that permission the way Discord spells it. The dashboard overview explains the rest of the interface.

Re-inviting Levlix

If several permissions are missing at once, the invite link is the fastest way back to a clean state. Open the invite page, pick the same server again and confirm the permissions. Discord adds them to the Levlix role that already exists instead of creating a second bot. You need Manage Server on that server, the same permission that was required to add Levlix in the first place. See Getting Started for the full invite flow.

Common Symptoms

If a permission is granted and the feature still fails, ask in the Levlix Support Discord.