Permissions & Roles
Understand the permissions Netrcol needs on Fluxer, how role hierarchy limits what the bot can do, and which action fails when a permission is missing.
Topics: permissions, roles, hierarchy, access, admin
There are two separate kinds of permissions to think about:
- Your permissions — what *you* need to configure Netrcol.
- Netrcol's permissions — what the *bot* needs to carry out each action.
Most "the command did nothing" problems come down to one of these two, or to role hierarchy.
Permissions you need
To open a server in the dashboard and change settings, you need the Manage Server permission on that server.
Individual chat commands require the matching permission — for example Ban Members to run !ban, or Manage Server to change the prefix or language. Administrators bypass all of these checks. Each command's requirement is listed in the Commands Reference.
Permissions Netrcol needs
Netrcol can only do what its own role allows. The simplest path is to grant Administrator — the invite flow requests it by default — but you can also assign granular permissions if you prefer tighter control.
Baseline
In any channel where Netrcol posts (logs, welcome messages, panels, announcements), it needs:
| Permission | Why |
|---|---|
| View Channel | To see the channel |
| Send Messages | To post |
| Embed Links | To send rich embeds |
| Read Message History | To enrich logs and edit its own messages |
Features that use reactions (ticket panels, reaction roles, games) also need Add Reactions.
Per-feature
| Feature | Permission the bot needs |
|---|---|
| Ban / Unban | Ban Members |
| Kick | Kick Members |
| Timeout, Warn, AutoMod timeouts | Moderate Members |
| Clear messages, AutoMod, Games | Manage Messages |
| Lock / Unlock / Slowmode, Tickets | Manage Channels |
Autorole, Register, Reaction Roles, Invite & Level rewards, !role | Manage Roles |
Change nicknames (!setnick) | Manage Nicknames |
Tip: The dashboard runs a live setup health check on each module's page. If Netrcol is missing a permission or a channel is misconfigured, you'll see a warning there before anything breaks.
Role hierarchy
This is the most common gotcha. For any action that assigns/removes roles or moderates members, Netrcol's highest role must sit above the target role or member in the role list.
For example, if you want Netrcol to give out a "Verified" role, the Netrcol role must be positioned *higher* than "Verified" in Server Settings → Roles. The same applies to moderation: Netrcol cannot ban or timeout a member whose highest role is above its own.
How to fix it
- Open Server Settings → Roles.
- Drag the Netrcol role up, above every role it needs to manage.
- Roles are ranked top-to-bottom, so higher in the list = more authority.
Note: A role can never manage itself or anything above it — this is a platform rule, not a Netrcol limitation. Even with Administrator, Netrcol still can't act on roles positioned above its own.
Recommended setup
For the smoothest experience:
- Grant Netrcol Administrator (or the granular permissions above).
- Drag the Netrcol role near the top of your role list.
- Keep it below your own staff/owner roles if you want, but above every role it manages.
Still not working?
- A command does nothing → check that *you* have the required permission, and that the command isn't disabled in the Moderation settings.
- Netrcol can't assign a role → it's almost always role hierarchy.
- No log / welcome messages → confirm Netrcol has Send Messages and Embed Links in that specific channel.
Next steps
- Finish the Getting Started guide
- Set your prefix and language
- Explore the Features Guide