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

# Permissions

This page will inform you about the permissions needed, and if they are not given, what things would not work.

# Permissions Overview

Setting up Seshy correctly ensures that all moderation, logging, and game integrations run without interruptions. This page covers why Administrator access is recommended, as well as a full list of individual permissions if you choose to configure roles manually.

## The Standard Setup (Administrator Permission)

For most servers, granting the **Administrator** permission to Seshy is the simplest and most reliable choice.

### Why Administrator Is Recommended

* **Automatic Overrides:** Administrator allows Seshy to bypass channel-specific permission locks, ensuring logging and ticket creation work instantly in newly created channels.
* **No Configuration Overhead:** You do not need to update permission setups every time Discord rolls out new channel types or permission flags.
* **Prevents Broken Commands:** High-level actions like timeout enforcement, role management, and channel management will never fail due to missing hierarchy rights.

## Custom Setup (Individual Permissions)

If your server policy prevents granting Administrator privileges, you must grant permissions individually. The table below outlines what each permission does, why Seshy or similar bots require it, and what features will break if it is turned off.

## General Permissions

| **Permission Name** | **Operational Purpose** | **Feature Impacted If Missing** |
| :- | :- | :- |
| **Manage Roles** | Assigns auto-roles, syncs staff ranks, and applies ticket access permissions. | Role assignment, auto-roles, and ticket permissions will fail. |
| **Manage Channels** | Creates temporary support threads, ticket channels, and automated categories. | Automatic ticket generation and channel setup scripts will fail. |
| **Kick Members** | Allows staff to remove problematic users using bot moderation commands. | Moderation kick commands will return a missing permissions error. |
| **Ban Members** | Allows staff to permanently ban abusive users and purge their recent messages. | Moderation ban commands and automated raid protection will fail. |
| **View Audit Log** | Tracks staff actions, bans, channel edits, and role changes across the server. | Security logging and moderation history feeds will stop updating. |
| **Manage Webhooks** | Sends fast, formatted log messages and integration feeds into your channels. | Detailed logging feeds and webhook notifications will fail. |
| **Moderate Members** | Applies standard Discord timeouts (chat mutes) to members. | Auto-moderation mutes and manual timeout commands will fail. |
| **Manage Nicknames** | Formats user display names according to server naming standards or rank rules. | Nickname enforcement and identity synchronization will fail. |

## Text Channel Permissions

| **Permission Name** | **Operational Purpose** | **Feature Impacted If Missing** |
| :- | :- | :- |
| **View Channels** | Allows the bot to read messages and see channels where it is placed. | The bot will ignore commands and remain completely inactive in that channel. |
| **Send Messages** | Posts command responses, status alerts, and automated messages. | The bot cannot respond to user commands or post updates. |
| **Embed Links** | Formats responses into structured cards with colors, fields, and organized layouts. | Commands will output as unformatted text, or fail to render entirely. |
| **Attach Files** | Sends transcript files, image attachments, and exported data files. | Ticket transcripts, log exports, and file uploads will fail. |
| **Read Message History** | Checks previous messages to execute purges, moderation filters, and context commands. | Message purges, chat filtering, and logging accuracy will break. |
| **Manage Messages** | Removes spam, cleans up old command outputs, and closes tickets. | Auto-moderation, message purges, and automated ticket cleanup will fail. |
| **Use External Emojis** | Displays custom UI icons, buttons, and status indicators in messages. | Custom status icons and buttons will display as broken text codes. |
| **Add Reactions** | Uses emojis for confirmation prompts, reaction roles, and user menus. | Reaction roles and multi-step confirmation prompts will fail. |

## Thread & Voice Permissions

| **Permission Name** | **Operational Purpose** | **Feature Impacted If Missing** |
| :- | :- | :- |
| **Create Public Threads** | Generates public discussion threads attached to community channels or announcements. | Forum discussions and public discussion threads cannot be created. |
| **Create Private Threads** | Opens private thread sub-conversations within staff or review channels. | Private staff thread discussions will fail to create. |
| **Send Messages in Threads** | Allows the bot to post inside existing discussion threads and forum posts. | The bot will be unable to respond inside active forum or thread posts. |
| **Connect & Speak** | Allows entry into voice channels for voice-based logging or stage events. | Voice channel features and automated voice status checks will fail. |
| **Move Members** | Transfers users between waiting rooms, support channels, or voice lounge areas. | Automated voice routing and staff move commands will fail. |


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