Sign in

How to Set Up Roles and Permissions in Fluxer

Roles are how you control what members can and can't do in your community. A well-structured role setup keeps things running smoothly as your community grows.

How Roles Work

Every community starts with a single role: @everyone. This role applies to every member automatically and acts as your baseline set of permissions. Any permissions you grant or deny on @everyone apply to the entire community by default.

Members can have multiple roles stacked on top of @everyone. Permissions from all of a member's roles are combined together. If any role grants a permission, the member has it, unless a channel-level overwrite explicitly denies it.

Creating Roles

Open Community Settings > Roles and click Create Role. Give it a name and optionally pick a color. The color shows up next to the member's name in chat, which makes it easy to tell roles apart at a glance.

A few naming tips:

  • Use clear, descriptive names like Moderator, VIP, or Bot Manager.
  • Avoid names that could be confused with Fluxer system features.
  • Keep the total number of roles manageable. You can always add more later.

The Role Hierarchy

Roles are ranked from top to bottom in the role list. This order matters. Members can only manage roles and members that sit below their highest role in the hierarchy. Drag roles up or down in the list to reorder them.

The community owner bypasses all permission checks and always sits above every role. Below the owner, a typical ordering looks like:

  1. Admin - full management permissions
  2. Moderator - can manage messages and members
  3. Special roles - VIP, event host, or other cosmetic/functional roles
  4. @everyone - always at the bottom

Put more powerful roles higher in the list. This prevents moderators from editing admin permissions and keeps the hierarchy predictable.

Setting Permissions

Each role has a set of permissions you can toggle on or off. They fall into a few broad categories:

General Permissions

  • Manage Channels - create, edit, and delete channels.
  • Manage Roles - create and edit roles below this role in the hierarchy.
  • Manage Community - change community name, icon, and settings.
  • Kick Members and Ban Members - remove people from the community.

Text Permissions

  • Send Messages - post in text channels.
  • Manage Messages - delete or pin other people's messages.
  • Embed Links - post links that generate previews.
  • Attach Files - upload images and files.
  • Mention Everyone - use @everyone and @here.

Voice Permissions

  • Connect - join voice channels.
  • Speak - talk in voice channels.
  • Mute Members and Deafen Members - silence others in voice.
  • Move Members - drag members between voice channels.

Administrator

The Administrator permission grants every permission at once and overrides all channel-level denies. Only give this to roles you trust completely. Most communities only need it on an Admin role held by a small group.

Channel Permission Overwrites

Roles set community-wide defaults, but you can override any permission on a per-channel basis. This is how you make read-only channels, private channels, and mod-only spaces.

For the full walkthrough on channel-level permissions, see How to Set Up Channels and Categories.

A channel-level deny always wins over a role-level allow. This lets you lock down specific channels even for roles that otherwise have broad permissions.

Assigning Roles to Members

Right-click a member's name (or open their profile) and select Roles. From there you can add or remove any role that sits below your highest role in the hierarchy.

For communities with an application or verification process, you can use bots to assign roles automatically based on reactions, answers, or other criteria.

Common Role Setups

Small Community (Under 50 Members)

  • @everyone - can send messages and join voice.
  • Moderator - can manage messages, kick members.
  • The owner handles everything else.

Two roles are enough. Don't overcomplicate things when everyone knows each other.

Medium Community (50-500 Members)

  • @everyone - basic chat and voice access.
  • Moderator - manage messages, kick and ban members.
  • Admin - manage channels, roles, and community settings.
  • Optional: VIP or Regular as a cosmetic role for active members.

A clear three-tier hierarchy covers most needs. Admins handle structure, moderators handle behavior.

Large Community (500+ Members)

  • @everyone - restricted by default (no @everyone mentions, limited file uploads).
  • Verified - assigned after passing an intro or verification step. Grants full chat access.
  • Moderator - manage messages, kick, ban, mute in voice.
  • Senior Mod - manage channels and lower roles, for experienced mods.
  • Admin - full management, small trusted group.
  • Optional: Event Host, Bot Manager, or other specialized roles.

Larger communities need tighter defaults and more granular role tiers. Lock @everyone down and use a verified role to gate access so new joins go through a checkpoint first.