Skip to main content
Permissions Banner The Permissions tab is where you control which roles can use Helply’s slash commands in a server. Use this tab to decide who can access each command and to optionally limit how often different roles can use /ask.

What the Permissions tab does

Control command access

Choose which roles are allowed to run each Helply slash command.

Restrict staff commands

Keep staff-only commands limited to the right roles.

Use server manager fallback

Leave commands empty to keep them limited to members with Manage Server.

Set `/ask` cooldowns

Add optional per-role usage limits for /ask.

Command permissions

Each command in the Permissions tab can be assigned to one or more Discord roles. Click a command to choose which roles are allowed to run it.

How command access works

  • If a command has one or more roles selected, only those roles can use it.
  • If a command is left empty, access is limited to members with Manage Server.
  • The exceptions are /help and /support, which anyone can run by default.
This makes it easy to keep commands restricted until you are ready to open them up more broadly.
The Permissions tab shows the Helply slash commands currently available for your server.To view the full command list and what each command does, see Commands.

/ask cooldowns

The Permissions tab also includes /ask cooldowns. This lets you add optional per-role limits for /ask, measured in messages per hour. For example, you can give trusted roles a higher limit while keeping a stricter limit for general members.

How /ask cooldowns work

Per-role limits

Cooldowns are configured per role.

Role priority

Higher roles override lower roles.

Up to 10 roles

You can configure cooldowns for up to 10 roles.

Default with `@everyone`

Add @everyone if you want a default cooldown for the whole server.
If no /ask cooldowns are configured, /ask will not have a role-based rate limit from this section.
1

Lock down staff commands first

Start by assigning sensitive commands to staff or admin roles only.
2

Decide which member commands should be public

Review whether broader roles should be allowed to use commands like /ask.
3

Add `/ask` cooldowns if needed

Set stricter limits for general members and higher limits for trusted roles.
4

Use `@everyone` for a default limit

Add @everyone if you want a baseline cooldown that applies across the server.

Commands

Learn what each Helply command does.

Overview

Configure core routing and support settings.

Actions

Manage ticket workflow automation.