Permissions

How exceed decides who can act

Most exceed commands require a permission to use them. Moderation commands need moderator-level access, configuration commands need admin-level access, and everyday commands are open to everyone. exceed works out whether someone is allowed by checking, in order:

1. The bot owner — has full access everywhere, always.
2. Native Discord permissions — the standard permissions Discord already gives a member (like Ban Members, Manage Roles, or Administrator). Anyone with Administrator passes every check.
3. Fake permissions — extra permissions you grant to specific roles inside exceed, without changing their real Discord permissions.
4. Staff roles — roles you mark as staff, which unlock elevated (moderator/admin-level) commands.

If none of these grant access, the command is refused.

Native Discord permissions

By default, exceed maps each command to the Discord permission that fits it. For example, ,ban requires Ban Members, ,prefix requires Manage Server, and the Setup Assistant requires Administrator. If your roles are already set up sensibly in Discord, exceed usually just works — your existing moderators can moderate, your admins can configure.

The exceed permissions it recognizes include administrator, ban_members, kick_members, moderate_members, manage_messages, manage_roles, manage_channels, manage_guild, manage_nicknames, view_audit_log, mute_members, move_members, and deafen_members.

Staff roles

You can mark certain roles as staff roles. Members in a staff role are treated as having elevated access for moderator- and admin-level commands, even if Discord hasn't given them those native permissions. This is handy when you want a "Trial Mod" or "Helper" role to use moderation tools without handing them real Discord moderation permissions.

Fake permissions

Fake permissions let you grant a single, specific permission to a role — purely inside exceed, with no change to the role's real Discord permissions. For example, you could let a "Giveaway Host" role use ban-gated tooling, or give a role manage_messages access for exceed without it gaining that power anywhere else in Discord.

Fake permissions are managed by the bot owner with the ,fakepermissions command (alias ,fp):

• ,fakepermissions add <role> <permission> — grant a permission to a role.
• ,fakepermissions remove <role> <permission> — take it back.
• ,fakepermissions list [role] — see what's granted.
• ,fakepermissions reset — clear all fake permissions in the server.

Per-command permissions on the dashboard

For finer control, open the Commands page in the dashboard. There you can manage every command individually for your server:

• Disable a command entirely so no one can run it.
• Restrict it to specific roles with allowed-roles, so only those roles may use it.
• Change the required permission if the default doesn't suit you.
• Block it in specific channels so it can't be used where you don't want it.
• Add custom aliases so members can trigger it by your own names.

This is the most precise layer: it lets you lock down or open up individual commands beyond what the default permission mapping does.

Putting it together

A command runs for a member when:

1. The member clears the command's permission check — as owner, via Discord permissions, a staff role, or a fake permission — and
2. The command isn't disabled (globally or in that channel) and any allowed-roles restriction on the Commands page permits them.

Next steps

• See every command and the permission it requires in the Commands reference.
• Learn how features themselves are switched on in Enabling Features.