> ## 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.

# FAQ

> This page combines practical troubleshooting with Headless-specific behavior. It does not assume another bot's causes or fixes apply here.

## A flag fails on iOS

If a command flag changed from `--` to an em dash `—`, turn off iOS Smart Punctuation or replace the character with two ASCII hyphens. Only commands that document flags accept them.

## A member can still send messages after mute

Headless configures mute roles, but Discord combines server permissions and channel overwrites. Check `@everyone`, member roles, channel exceptions, and the bot's Manage Roles permission/hierarchy; see Moderation Setup for the roles prepared by `.setupmute`.

## Headless is missing or left the server

These docs do not confirm an inactivity-removal policy. Check Discord's audit log, who removed the bot, service errors, and bot status. Do not use another product's removal reason to explain a Headless departure.

## A voice action fails

Creating Headless VC rooms requires Manage Channels and Move Members; channel overwrites and role hierarchy also apply. Run `.privatevc panel` to review setup.

## Setup

> **How do I invite Headless to my server?**
>
> Use the official site to start installation. Discord shows the requested permissions before you confirm.
>
> [Official site](https://headlesslabs.xyz/)

## Commands

> **What is the command prefix?**
>
> Public examples use `.`. Each server can keep a custom prefix; slash commands are available when registered.

> **Where can I find commands and examples?**
>
> The Commands page uses the public registry published by the bot. In Discord, query a category with `.help [section]` or `/help`. If the service is unavailable, it does not fill the page with stale examples.
>
> [Open Commands](https://headlesslabs.xyz/commands/)

## Dashboard

> **What can I manage from the Dashboard?**
>
> Discord OAuth identifies your account and server; every operation checks your permissions again. The web app only shows or changes modules authorized for the selected account and server.
>
> [Open Dashboard](https://headlesslabs.xyz/dashboard/)

## Security

> **Does Administrator make someone trusted by Anti-Nuke?**
>
> No. Headless separates native Discord permissions from Anti-Nuke capabilities and exemptions. Configure them explicitly.
>
> [Read Anti-Nuke](/docs/en/security/anti-nuke.md)

> **Does Smart Setup change settings immediately?**
>
> No. Recommend is read-only; Setup first produces a preview. Changes apply only after the owner reviews and confirms that preview.
>
> [View Anti-Nuke setup](/docs/en/security/anti-nuke.md)

## Steps

**1. Copy the error**

Record the server, channel, command, and time without sharing tokens or private data.

**2. Check the scope**

Distinguish user authorization, bot permissions, and Discord channel overwrites.

**3. Use safe diagnostics**

Check available status/diagnostic commands before retrying an action that deletes or sanctions.

> [!WARNING]
>
> Do not repeat a destructive command or sanction as a diagnostic step. For a server departure, check the audit log first; without that evidence this guide cannot know the cause.

## Related pages

* [Permissions](/docs/en/permissions.md)
* [Moderation setup](/docs/en/security/moderation.md)
* [Headless VC](/docs/en/voice/overview.md)


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