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

# Permissions & access

> Headless checks permissions per command and action. Permission to configure a feature does not grant permissions to the bot or change Discord channel overwrites.

## Actor permissions

Each command documents its requirement: for example, `.vanity` requires Administrator, `.alias` requires Manage Server, `.afklist` requires Manage Messages, and `.privatevc lobby` requires Manage Channels. Checks run in the server and can differ by subcommand.

### Actor-permission examples

```headless-command Syntax theme={null}
.vanity action <action>
```

```headless-command Example theme={null}
.vanity action log
```

```headless-command Syntax theme={null}
.alias list
```

```headless-command Example theme={null}
.alias list
```

```headless-command Syntax theme={null}
.afklist
```

```headless-command Example theme={null}
.afklist
```

## Bot permissions and hierarchy

In addition to actor authorization, Headless needs the native permissions required for the action. Review Manage Channels for channel changes; Manage Roles and role hierarchy for roles; and Move Members for relevant voice operations. An authorized command can still fail if Discord blocks the bot.

### Channel changes

```headless-command Syntax theme={null}
.privatevc lobby <channel>
```

```headless-command Example theme={null}
.privatevc lobby #Create-VC
```

## Virtual permissions

Fake Permissions is a separate, limited system. It does not edit Discord permissions; it provides virtual context only to Headless checks. Only the server owner or Headless owner can manage it, and the virtual `administrator` key substantially broadens access.

### Inspect virtual permissions

```headless-command Syntax theme={null}
.fakepermissions list [role]
```

```headless-command Example theme={null}
.fakepermissions list
```

## Steps

**1. Read the command requirement**

Open the feature guide and check both the actor's Discord permission and the bot's permissions.

**2. Check role and channel**

Review the bot role hierarchy and overwrites on the target channel.

**3. Test with minimum scope**

Try a test channel/member before granting broader access.

## Access, configuration, and support

> **[1. Sign in with Discord](/docs/en/dashboard.md)**
>
> OAuth2 identifies the operator and shows servers their account is authorized to manage. Membership alone is not enough; server access is checked again for sensitive actions.

> **[2. Per-server configuration](/docs/en/dashboard.md)**
>
> Modules keep their own settings. Channels, roles, and other values are validated for the selected server, and required permissions can differ by feature.

> **[3. Maintenance](/docs/en/dashboard.md)**
>
> The server view exposes health, recent activity, and last-sync status to help identify missing permissions or settings that have not synchronized yet.

> **[4. Safe changes](/docs/en/dashboard.md)**
>
> The API checks access again before accepting changes; some actions provide a preview before confirmation. Backups are not a setting in the public Dashboard and should not be assumed available from this guide.

> **[5. Support](/docs/en/common-issues.md)**
>
> Contact support when an issue requires checking bot permissions, an integration, or an incident. Never send tokens, passwords, or webhook secrets.

> [!WARNING]
>
> Do not grant the bot Administrator to fix an isolated permission error. Headless virtual permissions do not replace Discord's native access control.

## Related pages

* [Fake Permissions](/docs/en/security/fake-permissions.md)
* [Moderation setup](/docs/en/security/moderation.md)
* [Voice permissions](/docs/en/voice/permissions.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.