Why a server does or does not appear in your dashboard

Sign in with Discord

Selecting Dashboard opens Discord's authorization flow. Bozos does not ask you to create a second password for the website. After Discord sign-in, the dashboard can identify the account and request the server list needed to decide which communities you can manage.

Which servers appear?

A server is manageable when the signed-in account owns it or Discord reports that the account has Administrator or Manage Server permission. This rule is about your user account; it is separate from the permissions granted to the Bozos bot role.

If a server is missing

1. Make sure you signed in with the intended Discord account.
2. Open the server in Discord and confirm that account is the owner, Administrator, or has Manage Server.
3. If permissions were changed recently, refresh the dashboard or sign in again so the server list can be refreshed.
4. Check that you are looking at the correct Discord account if you use multiple accounts.
5. If the server still does not appear, use the official support server for help.

If Bozos is not installed yet

A manageable server can still need the bot itself. When Bozos is missing from a selected guild, the dashboard can route you through Discord's bot authorization flow. After the bot is added, you can return to that server's configuration.

Per-server settings stay separate

Bozos does not use one global configuration for every community. Music, moderation, Bozos Audit, birthdays, AFK, Scheduler and other dashboard options can be configured differently in each server you manage. Turning a system off in one server does not disable it in another.

Why a setting can look correct but still fail

The dashboard can save the intended configuration, while Discord permissions still determine whether the bot can actually perform an action. For example, a logging channel can be selected correctly but block the bot through channel overrides, or a moderation command can fail because the target's role is above the Bozos role.

Safe dashboard habits

• Use the official website and Discord authorization flow.
• Do not share session cookies, Discord tokens or account passwords with support staff.
• After recreating a channel or role, update any saved setting that pointed to the old Discord object.
• Test important moderation/logging settings in a controlled channel before relying on them during a real incident.

Quick troubleshooting checklist