Bozos Forever permission
The supported setup is to grant Bozos Forever Administrator when inviting/configuring it. This prevents individual feature permissions from becoming fragmented across moderation, music, logging and utility systems.
Administrator does not bypass role hierarchy
Discord's role order still decides whether Bozos can moderate a member. If a target member's highest role is equal to or above the highest Bozos role, Discord can reject actions such as kicks, bans or timeouts even though the bot has Administrator.
A practical setup is to place the Bozos role above normal member and moderation-target roles, while keeping trusted owner or protected staff roles above it if you do not want the bot to act on them.
Your dashboard access is separate from the bot's permissions
The dashboard checks the Discord account you signed in with. A server can appear when your account is the owner, has Administrator, or has Manage Server permission. This is different from the permissions assigned to the Bozos bot itself.
Channel overrides can still matter
Discord channels can have permission overwrites for specific roles or members. If a feature appears configured correctly but cannot post, connect, speak or view a channel, inspect that channel's overrides and make sure they are not explicitly denying the required access.
Why Bozos uses Discord IDs
Discord names are editable, but IDs are stable identifiers for a specific server object. A configured log channel, birthday role or scheduler target therefore needs the ID of the exact channel or role rather than relying only on its visible name.
Getting an ID
- Open Discord Settings and enable Developer Mode.
- Right-click the channel, role or user you want to identify.
- Choose Copy ID.
- Paste the numeric ID into the matching dashboard/configuration field.
Recreated objects get new IDs
If you delete and recreate a channel or role, Discord creates a completely new object with a different ID even if you reuse the same visible name. Update the saved Bozos setting after recreating anything used by the dashboard.
Common permission symptoms
- Moderation command fails: check the target's role position relative to Bozos.
- Audit log does not arrive: check the configured destination and channel access.
- Music cannot join: verify View Channel, Connect and Speak for that voice channel.
- Dashboard server is missing: verify the signed-in account has owner, Administrator or Manage Server access.
- A previously working destination broke after recreation: copy and save the new channel/role ID.
Recommended setup order
- Invite Bozos through the official website.
- Place the bot role correctly in the hierarchy.
- Open the dashboard with an account that can manage the server.
- Configure channels and roles using the current Discord objects.
- Test moderation, logging and voice behavior before relying on automation.