> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prowlbot.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Prowl Bot Permissions for Your Discord Server

> Learn how to control which roles and channels Prowl can access, and how to restrict bot commands to specific roles or channels in your server.

Permissions are the foundation of a well-run Prowl setup. Getting them right ensures the bot can do everything you need while preventing members from abusing commands or accessing features reserved for your staff.

## How Discord Permissions Interact with Prowl

Prowl is a Discord bot, so it operates within Discord's own permission framework first and foremost. Before Prowl's internal command restrictions are even checked, Discord itself determines whether the bot is **allowed to act** in a given channel or server.

Two layers govern what Prowl can do:

1. **Discord permissions** — what Discord allows Prowl to see and do (send messages, read history, manage roles, etc.).
2. **Prowl command restrictions** — which of your members are allowed to invoke specific Prowl commands.

Both layers must be satisfied. If Discord prevents Prowl from reading a channel, no Prowl feature will work there regardless of what you configure in the dashboard.

## Recommended Permissions at Invite

When you invite Prowl using the official link, it requests **Administrator** permissions by default. This is the simplest setup and ensures every feature works without you needing to manually grant individual permissions.

If you prefer not to grant Administrator, here are the minimum permissions Prowl needs to function across all features:

| Permission                    | Why It's Needed                                 |
| ----------------------------- | ----------------------------------------------- |
| Read Messages / View Channels | Required for all features to function           |
| Send Messages                 | Required to respond to commands and send alerts |
| Send Messages in Threads      | Required for thread-aware features              |
| Embed Links                   | Required for rich embed responses               |
| Attach Files                  | Required for logging exports                    |
| Read Message History          | Required for automod and message logs           |
| Manage Messages               | Required to delete rule-breaking messages       |
| Manage Roles                  | Required for role rewards and verification      |
| Kick Members                  | Required for moderation commands                |
| Ban Members                   | Required for moderation commands                |
| Moderate Members              | Required for timeout commands                   |
| View Audit Log                | Required for accurate moderation logging        |

<Warning>
  If you restrict Prowl's Discord permissions manually, some features may silently fail rather than displaying an error. If a feature isn't working, check bot permissions in that channel first.
</Warning>

## Prowl's Moderator System

Prowl has its own concept of who counts as a **moderator**. This is separate from Discord's permission system and determines who can use moderation commands like `/ban`, `/kick`, `/mute`, and `/warn`.

A member is considered a Prowl moderator if they meet **any** of these criteria:

* They have the **Administrator** permission in the server
* They have the **Moderate Members** permission
* They hold a role configured as a **mod role** in the Prowl dashboard

### Configuring Mod Roles

In the Prowl dashboard under **Moderation**, you can add one or more roles as mod roles. Members holding any of these roles can use moderation commands.

<Tip>
  Create a dedicated `@Moderator` role, assign it to your trusted staff, and add it as a mod role in the Prowl dashboard. This keeps your moderation team clearly defined.
</Tip>

## Channel-Level Restrictions

You can allow or deny Prowl in specific channels, giving you spatial control over where bot interaction happens.

**Denying Prowl in a channel:**

1. Open the channel in Discord and go to **Edit Channel → Permissions**.
2. Click **+ Add roles or members** and select **Prowl**.
3. Deny **Send Messages** and/or **View Channel** to prevent the bot from operating in that channel.

<Note>
  Prowl must have **Send Messages**, **Embed Links**, and **View Channel** permissions in every channel you designate as a log channel. Without these, logs will silently fail to post.
</Note>

## Restricting Commands to Specific Roles

You can use Discord's built-in integration permission settings to restrict which roles can use Prowl's slash commands:

1. Go to **Server Settings → Integrations → Prowl**.
2. You'll see a list of all Prowl slash commands.
3. Click any command to add role or channel overrides directly within Discord.

<Note>
  Discord's native integration permissions work independently from Prowl's mod role system. If you've configured mod roles, those members can always use moderation commands regardless of Discord's integration settings.
</Note>

## Resetting Server Data

If your configuration becomes complex or broken, you can reset Prowl's data for your server from the dashboard under **Settings**. This clears all stored configuration but does not affect Discord-level permission overrides.

<Danger>
  Resetting is permanent.
</Danger>