Permissions model

Three separate things decide whether Dispresso Bot answers you: whether Discord shows you the command, whether the module it belongs to is on, and whether your server has narrowed who may run it. Most confusion about permissions is one of those three, and they have different fixes.

Talking to the bot uses the same gates#

dispresso ban @user for spamming          the same check as !ban
dispresso make the level ups go to #levels  Manage Server
dispresso set your personality to chill     owner or admin
dispresso claim my daily                    anybody, runs as you

A sentence is not a way around any of this. dispresso ban @user runs the same code behind the same check as !ban and /mod ban, so a moderator who cannot ban by command cannot ban by asking. Changing a setting by talking (a channel, a role, a switch, a whole module) needs Manage Server, the same as the dashboard. Rebuilding the server, and turning the bot's talking off or on, are for the owner or an administrator. A member sentence like show me my profile is the command run as that member, with that member's cooldowns and that member's access. The settings you change by talking are the same rows you would change in /botdashboard or on the site, so all three doors agree.

Slash commands you cannot see#

Admin commands are published to Discord as requiring Manage Server, so members without it do not get them in the command list at all. /botdashboard is the clearest example. That is Discord's own gate, and Discord is where you change it: Server Settings, Integrations, Dispresso. You can open any command up to a role, or shut one off in a channel, without touching anything here.

Moderation: who can warn, and who can ban#

With nothing configured, each moderation command falls back to the Discord permission that matches it. Kick needs Kick Members, ban needs Ban Members, purge needs Manage Messages, lock and slowmode need Manage Channels, and the rest of it needs Timeout Members. Somebody who can already ban by hand can ban through Dispresso, and nobody else can.

That is usually not what a bigger server wants, so the Moderation Suite has a Staff access page in /botdashboard and on the site. Name a moderator role and a senior moderator role there and the Discord permissions stop mattering: your moderators get warn, kick, timeout, purge, slowmode and the channel locks, and ban, unban, jail, unjail and clearing warnings are held back for senior.

Below that you can override one command at a time, by role or by named member, which is how you hand somebody purge and nothing else. An override is absolute for that command: clearing its role list entirely means nobody can use it, rather than falling back to the Discord permission. Administrators always keep everything.

Member commands you want to narrow#

Things anybody can run, like !rank, !stats or !msgs, have a second control on their own module page: the channels they are switched off in, and the roles allowed to use them. Leave both empty and it stays open to everyone, which is what every server gets until it decides otherwise.

Fill either one in and Dispresso says so out loud when it refuses, naming the command and pointing at the dashboard. It does not go quiet on you. The server owner and anyone with Administrator are never caught by it.

The three that stay with the owner#

Anti Nuke, Server Backups and Auto Purge are not gated on Manage Server, because every administrator has Manage Server and a compromised administrator account is exactly what Anti Nuke exists to stand in front of. A backup is a full map of your server, and Auto Purge destroys messages for good.

Those three answer to the server owner and nobody else. The owner can grant a handful of named people access from the Moderation Suite, and Auto Purge keeps its own list, so trusting somebody with purge schedules does not also hand them your backups. Somebody who was granted access cannot grant it to anyone else. Leaving all three owner-only is the safer choice, and the denial message says so.

When somebody says a command did nothing#

Work down in this order. If Dispresso replied with a refusal, read it: it names the command and where to change it. If it said nothing at all, the message never reached it, and the usual cause is the server prefix. Check it with /server prefix, or mention the bot instead, which always works whatever the prefix is.

If the command exists but its module is switched off, nothing answers. If a slash command is missing from the list rather than refusing, it is Discord hiding it, not Dispresso, and the Integrations screen is where that lives. And if Dispresso refuses to act on one particular member, check where its role sits: it cannot touch anybody above it, and never touches the server owner.