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

# Fake Permissions

> Give your staff moderation power through misery without handing them real Fluxer permissions.

## What this solves

A moderator with a genuine `Ban Members` permission can do damage misery never sees — a script hitting the Fluxer API directly, a compromised account mass-banning through the app, or someone acting outside your logs entirely.

Fake permissions close that gap. Your staff keep working normally, but every action they take flows through misery, where it can be tracked, rate-limited, and caught by [antinuke](/security/antinuke).

## How it works

You assign a permission like `ban_members` to a role through misery. Members with that role can now run `,ban` — but their actual Fluxer permissions stay untouched, so the app's own ban option and any API access stay off-limits.

The result: full moderation capability, zero raw Fluxer power.

> [!WARNING]
>
> Every command on this page is restricted to the **server owner** and **co-owners**.

## Assigning permissions

```javascript Syntax theme={null}
,fakepermissions add (role) (permission)
```

```javascript Example theme={null}
,fakepermissions add @Mod ban_members, kick_members
```

> [!NOTE]
>
> Stack several at once by separating them with commas or spaces. `,fp add @Mod ban_members kick_members` works exactly the same.

misery rejects a permission a role already holds, so re-running a command won't create duplicates.

## Removing permissions

```javascript Syntax theme={null}
,fakepermissions remove (role) (permission)
```

```javascript Example theme={null}
,fakepermissions remove @Mod ban_members
```

## Reviewing your setup

Run `,fakepermissions list` to page through every role and the permissions attached to it.

## Wiping everything

`,fakepermissions reset` clears all fake permissions server-wide. misery asks you to confirm with a ✅ reaction first.

## Available permissions

See [Permissions](/resources/permissions) for the full list and what each one unlocks.

## Suggested setups

**Trial Mod** — enough to handle chat without touching membership.

```javascript theme={null}
,fp add @Trial Mod manage_messages, manage_nicknames
```

**Moderator** — chat control plus the ability to remove problem members.

```javascript theme={null}
,fp add @Moderator manage_messages, manage_nicknames, kick_members, mute_members
```

**Administrator** — adds bans, roles, and audit visibility on top.

```javascript theme={null}
,fp add @Admin manage_messages, manage_nicknames, kick_members, ban_members, manage_roles, view_audit_log
```

**Co-Owner** — one permission covering everything.

```javascript theme={null}
,fp add @Co-Owner administrator
```

> [!TIP]
>
> When you remove someone from staff, `,stripstaff (member)` takes away their staff roles and fake-permission roles in one go.


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