Levlix Server Health

Server Health is the page in your server's dashboard sidebar that lists what Levlix is missing to do what you switched on. Levlix checks every enabled module against the permissions it holds, the channels and roles you configured, and Discord's own state. Only the server owner, administrators and Levlix staff see it.

What the Page Shows

• One card per module with a problem, worst first. "Blocking" means the feature does nothing until you fix it; "degraded" means it works with something missing, for example without a rich message.
• A link to the module's settings page and a "How to fix" link into this guide for every finding.
• "Check again" runs the check now. The bot otherwise keeps the result for a short while.
• The count in the sidebar and the notice on the server overview show the same numbers.

Guild Permissions

The Levlix role lacks a permission the module needs server wide, for example Manage Roles for level roles or Timeout Members for moderation. Open Server Settings > Roles > Levlix and switch the permission on. If Levlix holds several roles, any of them may carry it. The full list per module is in the Bot Permissions guide.

Channel Permissions

Levlix has the permission on the server but a channel or category override takes it away, or the channel never granted it. Open the channel's settings > Permissions and allow the named permissions for Levlix (or a role it holds). Categories pass their overrides to synced channels.

Role Hierarchy

Discord only lets a bot give out roles that sit below the bot's own highest role. Open Server Settings > Roles and drag the Levlix role above every role it should hand out (level roles, birthday roles, join roles, shop roles, the mute role). Managed roles (bot roles, boosters) and @everyone can never be assigned; pick a normal role instead.

Deleted Channels and Roles

A setting points at a channel or role that no longer exists. Open the module's settings page and pick an existing one, or clear the setting.

Slash Commands

Discord refused to register Levlix's commands on this server, which happens when the bot was invited without the applications.commands scope. Invite Levlix again with the invite link from the dashboard; the existing settings stay.

Recent Failures

The page also lists what Levlix tried and Discord refused: a message it could not send, a role it could not give, a member it could not time out. Each row names the module, what was attempted, why Discord said no and how often it happened. Rows close on their own once a check finds the cause gone, or after seven days without a repeat. "Mark as resolved" closes one by hand; it comes back as "again since" if the failure repeats.

Notifications

Once a day Levlix checks your server and sends a message when it finds new problems: to the server owner, to up to ten administrators, or into a channel you pick. The card at the top of the Server Health page sets who gets it and whether degraded findings count too. The first check only records what is there and sends nothing, so switching Levlix on does not start with a wall of messages. A problem is reported once; it comes back only if it was fixed and then breaks again. If a message cannot be delivered, for example because direct messages are closed, the page shows the reason and Levlix tries again the next day.

When Levlix Is Offline

The page then says "Live check unavailable". Problems recorded earlier still show once the bot is back and has run a check.