Improvements to permissions and management has been one of the most requested improvements for slash commands and other kinds of application commands. Our existing system just isn't cutting it, so we set out to make a new system.

We talked to admins, moderators, developers, and a bunch of people who work here. We wanted to solve the following problems:

• As a moderator, I need to be able to control who can use certain commands
• As a moderator, I need to be able to control the channels in which people can use commands
• As a moderator, I want to use more bots, but they don't all have permission systems to keep my community safe
• As a developer, I want to be able to put sane defaults on my commands so that they don't get abused before moderators have a chance to tune permissions

So, welcome to your new application command permissions page.

<aside> ⚠️ The following designs are all work in progress as we finish up the design and feedback phase. What you see may change!

</aside>

We'd share a Figma prototype, but last time we did that, it...crashed. Woops.

Generality and Granularity

When you open an app from your integrations page, you'll be able to manage access to its commands. You can start by setting role, member, and channel access on the application itself.

By default, applications are available to @everyone in # All Channels. An "on" toggle grants access; an "off" toggle denies access. So, if you wanted to make all of an app's commands "private", you could remove access from @everyone.

Let's say you want to only certain people to use an app. You can add and deny permissions from both roles and members.

Only BEARo, Lone Wanderer, and Arame have access. No one else!

You can also allow or deny access in specific channels or categories.

Synced and Un-sunk

Sometimes, you might want to control access to a specific command. You can do that!