Permissions

There are two sides to permissions in Dexy: what Dexy itself is allowed to do in your server, and what your members are allowed to do with Dexy. This page covers both, starting with the things most servers set up first.

Set up permissions on the dashboard#

Everything about who can use and manage Dexy is on one page.

1. Open your server on the dashboard and go to Manage ▸ Permissions.
2. Under Command access, choose what members can do with commands: Use every command, Look up the server, and themselves, Only look up themselves or Nothing.
3. Under Dashboard access, choose who can open the stats pages: Public, Members only or Admins only.
4. Under Role permissions, use Add a role to add a role, then tick what it may do: View stats, Use commands anywhere, Change settings, Manage counters, Manage activity roles or Moderate.

5. If you're an Administrator, pick a Dexy admin role and decide whether Manage Server counts as a Dexy admin.
6. Press Save changes in the bar at the bottom.

The rest of this page explains each of these in detail.

What Dexy needs#

Dexy works with Fluxer's normal role permissions. Give its role these, either when you add it or later in your server's role settings. Run d!diag at any time to see which ones are missing and what each is for. It also checks what Moderation, Auto-mod, Logging, Welcome, Auto Roles and Reaction Roles need while they're on, and the channels Dexy posts in for them.

Needed everywhere#

Needed for some features#

For the mod log, Dexy also needs View Channels, Send Messages and Embed Links in that channel. Log channels need View Channels and Manage Webhooks instead: event logs come from the Dexy Logs webhook Dexy makes there (see How posts are sent). If the webhook can't be used, Dexy posts as itself, which needs Send Messages and Embed Links. Welcome's join and leave channels need View Channels, Send Messages, Embed Links and Attach Files (for the welcome image). The appeal review channel needs those plus Add Reactions (for ✅ and ❌) and Manage Messages (to take off reactions from people who can't decide). A reaction-role message's channel needs Add Reactions, Read Message History and Manage Messages, plus Send Messages and Embed Links when Dexy posts the message. d!diag and the dashboard's setup check report a channel Dexy can't post in or that was deleted; the Logging page and d!logs test report log channels too.

Role order#

Fluxer only lets Dexy act on members and roles below its own highest role. So:

• To time out, kick or ban someone, Dexy's highest role must be above theirs.
• To give or take a role (activity roles, Auto Roles, reaction roles, d!role add), that role must be below Dexy's highest role.
• Nobody can act on the server owner, and Dexy never acts on itself.

Moderators have the same rule: you can only act on members whose highest role is below yours (the owner can act on anyone), and only give or take roles below your own highest role.

Who can manage Dexy#

A Dexy admin can run every Dexy command and change every setting in a server. These people are Dexy admins:

• The server owner.
• Anyone with Administrator.
• Members of the server's Dexy admin role, if one is set.
• Anyone with Manage Server, as far as the Manage Server setting below allows.

Manage Server#

By default, the Manage Server permission makes someone a Dexy admin. You can narrow that with d!settings manageserver or on the dashboard under Permissions:

On the dashboard, an Administrator switches Manage Server counts as a Dexy admin on or off under Manage ▸ Permissions ▸ Manage Server, and picks Who counts.

Only Administrators (and the owner) can change this, so nobody can lock others out or remove their own access with it. People it leaves out keep whatever their roles get from role permissions below, and can still view stats if dashboard visibility lets them.

The Dexy admin role#

Pick one role whose members count as Dexy admins:

d!settings elevate @Mods
d!settings elevate off

d!settings elevate @Mods
d!settings elevate off

On the dashboard it's Manage ▸ Permissions ▸ Dexy admin role.

Only Administrators can set it, and only to a role that has Manage Server itself. That's checked every time the role is used: if the role loses Manage Server, its members stop counting as Dexy admins. The Dexy admin role passes every check except the ones that need Administrator (setting the Dexy admin role and the Manage Server choice).

Role permissions#

Role permissions let a role use parts of Dexy without being a Dexy admin. A member gets everything any of their roles allows. Set them with d!settings roles or on the dashboard's Permissions page.

On the dashboard, these are the columns of the table under Manage ▸ Permissions ▸ Role permissions: View stats, Use commands anywhere, Change settings, Manage counters, Manage activity roles, Manage auto & reaction roles and Moderate.

In chat, some examples:

d!settings roles @Mods settings counters
d!settings roles @Helpers +view
d!settings roles @Mods none
d!settings roles

d!settings roles @Mods settings counters
d!settings roles @Helpers +view
d!settings roles @Mods none
d!settings roles

The last one lists every role that has permissions. You can use all for every area, or +area and -area to add or remove one. Up to 50 roles can have permissions.

Appeal reviewers and deciders#

Appeal reviewer and decider roles aren't role permissions: they're part of the appeal settings, set with d!appealset reviewers and d!appealset deciders or under Moderation ▸ Appeals on the dashboard. They only reach appeals:

• Reviewer roles can read appeals and add notes.
• Decider roles can do that and accept or reject them.

Members whose only access is one of these roles see just Moderation ▸ Appeals on the dashboard, not the rest of Moderation or any other page. Changing the appeal settings, blocking people from appealing and deleting appeals need a Dexy admin or a role with moderation. See Appeals.

What stays with Dexy admins#

These can't be given through role permissions. Only Dexy admins can:

• Change role permissions, the Dexy admin role and dashboard visibility.
• Reset every setting with d!settings reset.
• Open the dashboard's Permissions and Audit log pages.

Setting the Dexy admin role and the Manage Server choice need Administrator.

The full list of which permission and which area each command needs is in the permissions reference.

Command access#

Command access decides how far members can go with Dexy's commands. Set it with d!settings access or under Manage ▸ Permissions ▸ Command access on the dashboard.

d!settings access restricted
d!settings access everyone

d!settings access restricted
d!settings access everyone

Dexy admins and roles with commands are never limited by this.

Command channels#

You can limit the channels where commands work. In whitelist mode (the default) commands only work in the listed channels; in blacklist mode they work everywhere except those. An empty list means every channel. On the dashboard they're under Manage ▸ General ▸ Command channels. In chat:

d!settings channels add #bot-commands
d!settings channels mode blacklist
d!settings channels clear

d!settings channels add #bot-commands
d!settings channels mode blacklist
d!settings channels clear

Only the exact channels listed count: a category doesn't cover its channels. Up to 50 channels can be listed. Dexy admins and roles with commands can use commands anywhere.

Commands that always work#

d!help, d!invite, d!links, d!ping and d!privacy work for everyone, in any channel, whatever command access and command channels say.

Dashboard visibility#

Dashboard visibility decides who can open this server's stats pages on the web. Visitors can only look; changing anything still needs the right permission. On the dashboard it's Manage ▸ Permissions ▸ Dashboard access.

Roles with view can always see the stats pages. Only Dexy admins can change this.

If your access changes#

Dexy checks your permissions again for every change you make on the dashboard. It asks Fluxer each time, so a role taken away a second ago already counts. This applies to Manage Server, Administrator, the Dexy admin role, role permissions and moderation permissions like Ban Members, Kick Members and Moderate Members.

Open dashboard pages react right away:

• You lost access to the server (your role was removed, the Dexy admin role changed, Manage Server stopped counting, or you left): the page is covered with "Your access to server changed. You can't manage it anymore." Nothing you were editing is saved. After a few seconds you go back to your servers, or press the button to go now.
• You lost part of it (say, moderation but not settings): the page reloads and the sidebar shows only what you can still open. If the page you're on is no longer yours, you're offered the Overview.
• You got more access: the page refreshes quietly.

If a save is refused because your access changed in the middle of an edit, you see the same message, and the draft isn't sent again. Moderation actions also check the role order every time: if your highest role is no longer above the member's, the action is refused.

Troubleshooting#

"You need Manage Server… to do that." The command needs a permission you don't have. Ask a Dexy admin to give one of your roles the matching area with d!settings roles, or to make you a Dexy admin.

A command does nothing at all. Command access or command channels are blocking it; Dexy stays quiet so channels don't fill with refusals. Try in another channel, or ask an admin to check d!settings.

"I can't time them out: their highest role isn't below mine." Move Dexy's role above the member's highest role.

Manage Server stopped working for me. An Administrator may have changed the Manage Server choice. Check it with d!settings manageserver.

The Dexy admin role stopped working. The role probably lost Manage Server. Give it back, or pick another role.

Something else is off. Run d!diag: it lists missing permissions (including what the modules you turned on need), channels Dexy can't see or can't post in, and counters with problems.