Permissions and roles

Fluxer has no slash commands: it can't hide a command from members who aren't allowed, like Discord does. The bot checks everything itself, in this order, on every command:

Each refusal is a short reply deleted after 5 seconds, together with your command. The permission name is written as in Fluxer's API ("Ban Members"): the table Permission required by each command gives the name shown in Fluxer's settings.

On invite

The invite link asks for Administrator: it is the simplest option, and what the bot expects. Without it, it needs at least:

Where the bot's role sits

On Fluxer as on Discord, a role can only give roles placed below it, and a member can only sanction members whose highest role is below theirs. Fluxer has one more rule:

Put the Dispatch.IO role above:

• the roles it gives (welcome, level and flame rewards, role panels, !role-all);
• the members it sanctions (!timeout, !kick, !ban, anti-raid) or renames (flames, !rename).

The bot never gives a role placed above its own, nor a "dangerous" role (Administrator, Manage community, Manage roles, Ban, Kick…) through a role panel.

Permissions checked per command

Before some commands, the bot checks that it has the permissions it needs, and replies "I'm missing the … permission" otherwise:

For the others, a missing permission simply makes the action fail (and a Permission error log is posted in the Server logs channel when planned).

The Dispatch.IO team commands (!badge, !manage-badge, !flag) only answer the bot's creators.

On top of Fluxer permissions, the bot knows two staff role types saved for each community: ADMIN and MODO. On Fluxer they are mostly used to protect:

• a member with an ADMIN role can only be sanctioned by the owner;
• a member with a MODO role can only be sanctioned by the owner or an administrator (ADMIN role or Administrator permission);
• a MODO (or ADMIN) role also lets you view other members' infractions with !infractions @member.

The moderation commands protect the owner and the staff. Each refusal shows a clear message, for example "You cannot ban a member with a role higher than or equal to yours.".

"Above" follows Fluxer's rule: higher position, or same position and older role.

The community owner always has every permission: they can use every command and access the dashboard. The bot also gives them these rights:

• Protection: they can't be targeted by !ban, !kick, !timeout or !unban.
• Sanctioning the staff: they are the only one who can sanction a member with an ADMIN role.
• Anti-raid: they are on the whitelist of every protection as soon as the bot arrives.
• Alerts: as long as no emergency mention is set on the website, they are the one mentioned on critical logs (anti-raid, sanctions).
• Infractions: together with members who have Administrator, they can delete an infraction (link sent with !infractions).
• Nickname: they are never renamed by flames.

Rights go through the Fluxer permissions of your roles (Community settings → Roles). Example for the Café des Devs community:

For protection between staff members, think of the hierarchy: put @Moderators above @Members, and the bot's role above all.

Changes made on the website are logged in the Server logs channel, with their author's name. Every setting is detailed in Bot configuration.

Website account roles (Dispatch.IO team, administration pages) are a separate system: see Managing permissions.