---
title: "Controlling who can use your commands"
description: "Restrict FNLB bot commands to owners, admins, whitelisted users, friends or party members from the category settings."
canonical: https://fnlb.net/support/bot-setup/command-permissions
markdown: https://fnlb.net/support/bot-setup/command-permissions.md
---

# Controlling who can use your commands

Restrict FNLB bot commands to owners, admins, whitelisted users, friends or party members from the category settings.

## Why restrict commands?

By default, anyone who can reach your bot can use most commands. If you share a bot with friends, or run bots in public parties, you can limit who is allowed to control it.

Permissions live in the category settings, so every bot in a category follows the same rules.

## User roles

The **User Management** section defines the people involved:

| Role | What it means |
| --- | --- |
| Owner | You, plus any extra owners you add |
| Admin | Trusted helpers with more access than regular users |
| Whitelisted user | A user you explicitly allow |
| Blacklisted user | A user who is always blocked |

Extra owners and admins do not need to be in your party to run owner or admin commands.

## Command restrictions

The **Command Restrictions** section decides which commands each group may use:

| Setting | Effect |
| --- | --- |
| Owner commands | Only owners can use them |
| Admin commands | Only admins and owners can use them |
| Whitelist user commands | Only whitelisted users, admins and owners |
| Friends only | Only the bot's friends |
| Party members only | Only players currently in the bot's party |
| Whisper only | Commands must be whispered to the bot |

Turn on only the restrictions you need, and leave the rest off.

## See what you can use

The `help` command only lists the commands **you** are allowed to run, so it always reflects the current restrictions. Use it to check whether a command is limited before assuming it is broken.

If a command seems to be ignored, see [Commands are not working](https://fnlb.net/support/troubleshooting/commands-not-working.md).