Skip to main content
QMod’s staff permission system lets you delegate moderation commands to specific members without handing over full Discord permissions. Instead of allowing unlimited bans or mutes, you define exactly what a staff member can do and how many times they can do it — per day, per week, or on any reset schedule you choose. Every action is logged to a channel of your choosing, keeping a transparent record of all staff activity.

​
Set up staff permissions

1
Begin by running the /admin-mod staff setup command. Choose the channel where all moderation actions performed by staff members will be logged.
2
Click the Rules button to open the rules panel. Here, you can view existing staff moderation rules and configure limited mod actions for specific staff.
3
Click Add to create your first rule. The rule card will turn red to indicate missing required values, and Quarky will display exactly which fields still need to be completed.
4
Select the staff member the rule applies to and choose the moderation action you want to allow: mute, kick, or ban.
5
Click Config to fill in the remaining values:
  • Maximum allowed number — how many times the action can be used
  • Duration reset — when the action limit resets
  • Rule name (optional)
  • Password (optional) for added security
When finished, click Submit. The rule will turn green once all required fields are complete.
6
After completing one rule, you can continue adding more. Up to 25 staff rules can be created under the Premium Tier, each with different targets, actions, and limits. When all your rules are configured, click Save.

​
Available mod commands

Once a staff rule is in place, the targeted member can use the corresponding /mod subcommand. The available commands are:
CommandAction
/mod muteMutes a member
/mod unmuteUnmutes a member
/mod kickKicks a member from the server
/mod banBans a member from the server
/mod unbanUnbans a previously banned member
/mod logViews the mod action log
By default, these commands are accessible to server admins only. To let members with a specific role use them, adjust Discord’s slash command permissions for your server. See the Role-Based Permissions guide for step-by-step instructions.
Having role-based access to a /mod command is not enough on its own. A staff member must also have a targeted rule set for that action — otherwise Quarky will not allow the command to execute.

​
Detailed example

A rule is set for @AAA that allows them to run the /mod mute command up to 3 times per day, protected by a password. When @AAA uses /mod mute for the first time, Quarky prompts them to enter the password configured in the rule. If a password was specified in the rule, Quarky asks for it here. If the password is correct and the target member has a lower role than @AAA, the mute action is applied. A log entry is sent to the previously configured alerts channel, showing who used the command, on whom, and when. If @AAA attempts to use /mod mute for the fourth time on the same day, Quarky blocks the action and explains that the daily limit has been reached. Quarky responds with the configured limit warning. If @AAA tries to use another command like /mod ban, Quarky rejects it because the rule only grants permission for the mute command.
Use passwords for high-impact actions like /mod ban to add an extra layer of accountability and prevent accidental or unauthorized use.