Role Restrictions

Control who can use a work command.

Role restrictions let you decide which members are allowed to use a specific work command. This is useful for roleplay servers, progression systems, staff-only jobs, or special event commands.

If no roles are selected, the command is available to everyone by default.

🪄 How Role Restrictions Work

Inside the Work Command setup, you’ll see a field called:

Required Roles

This is a simple dropdown where you can select one or more roles.

Only members with at least one of the selected roles will be able to use the command.

🌸 Example: Magical Girl Baking Job

For our /bake command, imagine you only want magical trainees to use it.

In Required Roles, select:

  • @Murasaki (or any magical-role you’ve created)

Now:

  • Members with @Murasaki can use /bake

  • Everyone else will be blocked from using the command

No extra setup needed.

Common Use Cases

Role restrictions are great for:

  • 🧙 Roleplay professions

  • 🎓 Progression-based jobs

  • 🎟️ VIP or supporter perks

  • 🛡️ Staff-only or mod commands

  • 🎉 Event-exclusive activities

They help commands feel earned, not generic.

💡 Tips:

  • Keep early jobs open to everyone

  • Lock advanced jobs behind roles

  • Use roles to guide progression

  • Avoid over-restricting casual commands

If everything is locked, new members may feel stuck. Balance is key

🌟 Why This Matters

Role restrictions:

  • Add structure and clarity

  • Prevent misuse of powerful commands

  • Encourage role progression

  • Make roles feel meaningful

When access is intentional, work commands feel like part of a system, not just buttons.

Last updated