Overview
Give each command its own availability, channel, role, cooldown, and cleanup rules without changing anyone's Fluxer permissions.
What Command Policies can do
- Disable commands - hide commands your community does not use.
- Restrict channels and roles - only allow a command where and for whom it makes sense.
- Add cooldowns- slow down commands without changing the bot's built-in limits.
- Clean up invocations - delete the trigger message after the command runs.
- Reset safely - remove all custom rules for one command and return it to its defaults.
Permission required
Manage Guild
Opening the policy editor
Run f!policy with no command to see the overview, or add a command name to open its policy editor:
f!policy
f!policy giveaway
f!policy pollsCommand aliases work too. For example, f!policy gw opens the policy for Giveaways. Use f!help if you are not sure which command name to use.
The same settings are available in the dashboard under Configuration, on the Command policies tab.
Policy settings
| Setting | Default | What it controls |
|---|---|---|
| Enabled | On | Whether the command can be used at all. |
| Allowed channels | All text channels | The channels where the command is accepted. An empty selection means every text channel. |
| Allowed roles | No role requirement | The roles that may use the command. An empty selection means no role requirement. |
| Cooldown | The command's global cooldown | An optional longer cooldown, up to one hour. |
| Invocation cleanup | Off | Delete the message that triggered the command. |
Only commands that are available to the community can be configured. Owner-only commands are not part of the policy list.
What cleanup does
Invocation cleanup deletes the trigger message after the bot reads the command. It does not delete the bot's response. This is useful for keeping a commands channel tidy without removing the result.
Disabled commands in help
Commands disabled by policy are separated in the help menu, so members can see that the command exists but is unavailable in this community. Re-enable it from the policy editor or the dashboard when you need it again.
Common uses
- Keep giveaway creation inside a staff-only channel.
- Disable commands that your community does not use without removing the bot.
- Allow reaction roles only for members with a verified role.
- Add a longer cooldown to a command that is being spammed.
- Delete trigger messages in a commands channel while keeping bot responses visible.
Resetting a command
The reset option restores a command to its defaults: enabled, all text channels, no role requirement, the global cooldown, and cleanup off. It only affects the command you are editing and removes its custom policy record.
Dashboard
Open your community's dashboard and go to Configuration, then Command policies. Select a command to edit the same settings without running a command.