Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.celestia.rest/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

The Fake Permissions system allows server owners to grant roles the ability to use moderation commands through the bot — without assigning actual Discord permissions to those roles. This acts as a security layer that keeps destructive native Discord actions out of reach while still allowing trusted staff to moderate through the bot.

​
How It Works

When a role is granted a fake permission such as BanMembers, members with that role can use the bot’s ban command — but they still cannot use Discord’s native ban feature directly. This means even if a moderator goes rogue, they cannot mass-ban, nuke channels, or cause server-wide damage through the Discord client or external scripts.
Fake permissions are enforced at the bot level only. They have no effect on what users can do natively in Discord.

​
Access Control

Only the server owner can manage fake permissions. This is intentional — granting fake permissions is a high-trust action and should not be delegated.

​
Commands

Grant one or more fake permissions to a role.
~fp add <role> <perm1, perm2, ...>
Aliases: fakepermissions Permissions: Server Owner only
Override all existing fake permissions for a role with a new set. Any permissions not included in the new list will be removed.
~fp edit <role> <perm1, perm2, ...>
Aliases: fakepermissions Permissions: Server Owner only
This completely replaces the existing fake permissions for the role. Use fp add if you only want to add new ones.
Remove specific fake permissions from a role without affecting others.
~fp remove <role> <perm1, perm2, ...>
Aliases: fakepermissions Permissions: Server Owner only
View all roles with fake permissions in the server, or view the permissions for a specific role.
~fp list
~fp list <role>
Aliases: fakepermissions Permissions: Server Owner only
View all valid fake permissions that can be assigned to a role.
~fp types
Aliases: fakepermissions Permissions: Server Owner only

​
Available Fake Permissions

The following permissions can be granted as fake permissions. Permission names are case-insensitive and underscores are optional (e.g. ban_members, BanMembers, and banmembers all work).

Administrator

Grants access to all fake-permission-gated commands. Acts as a wildcard.

BanMembers

Allows using ban-related moderation commands.

KickMembers

Allows using kick-related moderation commands.

ManageMessages

Allows deleting messages and using purge commands.

ManageNicknames

Allows changing nicknames of other members.

ManageRoles

Allows using role management commands.

ModerateMembers

Allows timing out members.

MuteMembers

Allows muting members in voice channels.

DeafenMembers

Allows deafening members in voice channels.

MoveMembers

Allows moving members between voice channels.

ManageChannels

Allows using channel management commands.

ManageGuild

Allows using server settings commands.

ViewAuditLog

Allows viewing the server audit log via the bot.

ManageWebhooks

Allows managing webhooks through the bot.

ManageGuildExpressions

Allows managing emojis, stickers, and soundboard sounds.

ManageThreads

Allows managing threads in the server.

​
Administrator Fake Permission

The Administrator fake permission is a special wildcard that grants access to all commands gated by any fake permission check. Assigning it to a role is equivalent to granting every individual fake permission at once.
Only assign the Administrator fake permission to highly trusted roles. Members with this fake permission will be able to use all moderation commands through the bot.

​
Permission Input Formats

All of the following formats are valid when specifying permissions:
InputResolves To
ban_membersBanMembers
BanMembersBanMembers
banmembersBanMembers
manage_messagesManageMessages
MANAGEMESSAGESManageMessages

​
Security Model

Fake permissions are designed with security as the primary goal:
  • No Discord-level access — Fake perms only affect what commands the bot allows. They do not modify Discord roles or permissions in any way.
  • Owner-only management — Only the server owner can assign or revoke fake permissions.
  • Bot-enforced — All checks happen server-side in the bot before any action is taken.
  • Revocable instantly — Permissions can be removed at any time with fp remove or overridden entirely with fp edit.
If a user has both a real Discord permission and a fake permission for the same action, either one is sufficient to use the command.

​
Best Practices

  • Use BanMembers and KickMembers for your moderation team instead of giving them real Discord ban/kick perms.
  • Use ManageMessages for chat moderators who need to purge messages.
  • Reserve Administrator fake permission only for senior staff you fully trust.
  • Combine fake permissions with the permit system to further restrict which commands each role can access.
Fake permissions do not protect against users who already have real Discord permissions. Always review your server’s role hierarchy alongside your fake permission setup.