Fake Permissions

Fake permissions let staff use Antidote moderation commands without native Discord permissions.

A moderator with fake ban_members can use ban through Antidote. They still cannot use Discord’s own ban button, Discord’s native timeout, or any other Discord client action that needs the real permission.

That is the point. Staff can moderate through the bot. They cannot mass-ban with a script against the Discord API, because Discord itself will refuse.

This is not the same as Antinuke. Antinuke punishes people who already have Discord permissions and start wrecking the server. Fake permissions keep those Discord permissions off staff in the first place.

Why use it

Give moderators a Discord role with no Ban Members, Kick Members, or Administrator. Grant the matching fake permissions to that role.

They can still:

• Ban, kick, timeout, and purge with Antidote commands
• Change nicknames or manage messages with Antidote, if you granted those flags
• Browse Discord’s audit log with audit, if you granted view_audit_log

They cannot:

• Open Discord’s native ban / kick / timeout UI
• Run a selfbot or raid script that hits Discord’s API as them
• Change Fake Permissions themselves, even with fake administrator

Pair this with Antinuke so leftover native permissions still cannot nuke the server.

Requirements

Requirement	Why
Server Premium	Fake Permissions is a premium server feature.
Server owner	Only the guild owner can grant, remove, or reset. Discord admins who are not the owner cannot.
Antidote’s own permissions	The bot still needs the real Discord permission to carry out the action. If Antidote cannot Ban Members, ban fails even when the user has fake ban_members.

How it works

1. You grant permission names to a role, not to a user.
2. Anyone with that role is treated as having those flags for Antidote command checks.
3. Discord’s own permissions are unchanged.
4. Fake administrator passes every user command permission check. It does not give Discord Administrator, it does not skip role hierarchy, and it does not let them manage Fake Permissions.

Antidote still respects:

• Role hierarchy (you cannot moderate someone above you)
• Channel-specific checks on some commands (for example nuke still looks at native Manage Channels on that channel)
• Bot permissions (Antidote must actually be allowed to do the action)

Viewing the audit log

Staff with native or fake view_audit_log can run audit (aliases: auditlog, logs).

Command	What it does
audit [user]	Latest Discord audit log, paginated with Previous / Next. Optional user is who performed the action.

The bot still needs real View Audit Log in the server. The fake flag only lets the user run the command.

Quick setup

1. Create or pick a staff role with no dangerous Discord permissions.
2. Open Dashboard → Fake Permissions, or run fakepermissions in Discord.
3. Grant the role a preset (Moderator, Administrator, or Co-Owner) or pick flags yourself.
4. Confirm with fakepermissions list.
5. Have a test moderator run a prefix command such as ban. It should work. Discord’s native ban should still fail for them.

Dashboard

Only the server owner can open this page. Everyone else is sent back to the server list.

On a free server the page is visible so you can read it, but Grant, chip remove, and Reset are locked. Use Get Premium to unlock.

On a premium server:

1. Pick a role.
2. Pick one or more permissions, or click a preset.
3. Click Grant.
4. Granted flags show as chips under that role. Remove one chip to revoke that flag.
5. Reset all clears every grant on the server (you get a confirm prompt).

Presets fill the permission list. You still click Grant after picking a role.

Commands

All of these are server owner only and need Server Premium. Aliases: fakepermissions, fakeperms, fp.

Command	What it does
fakepermissions	Overview, examples, and a dashboard link
fakepermissions grant <role> <permissions>	Add flags to a role. Alias: add
fakepermissions remove <role> <permissions>	Take flags off a role
fakepermissions list [role]	Show all grants, or only one role
fakepermissions reset [role]	Clear every grant, or only one role

Examples

fakepermissions grant @Moderator manage_messages, moderate_members, manage_nicknames, kick_members
fakepermissions grant @Admin ban_members, kick_members, manage_roles
fakepermissions grant @Co-Owner administrator
fakepermissions remove @Moderator kick_members
fakepermissions list
fakepermissions list @Admin
fakepermissions reset @Moderator
fakepermissions reset

You can mention the role, paste its ID, or type its name. Permissions are comma-separated. Names are snake_case (ban_members). BanMembers and timeout_members are also accepted.

Recommended presets

These match the dashboard buttons.

Moderator

Good for day-to-day chat staff. Do not give this role Ban Members or Administrator in Discord.

Permission	Lets them use
manage_messages	Delete / purge messages through Antidote
moderate_members	Timeout, mute, warn, and similar
manage_nicknames	Change nicknames through Antidote
kick_members	Kick through Antidote

fakepermissions grant @Moderator manage_messages, moderate_members, manage_nicknames, kick_members

Administrator

Adds bans and role management through the bot. Still keep native Discord Administrator off.

Extra permission	Lets them use
manage_roles	Role commands through Antidote
ban_members	Ban / unban through Antidote

fakepermissions grant @Admin manage_messages, moderate_members, manage_nicknames, kick_members, manage_roles, ban_members

Co-Owner

Fake administrator passes all Antidote user permission checks. It is the widest bot-side grant. They still cannot:

• Use Discord’s native Administrator tools
• Change Fake Permissions (owner only)
• Bypass role hierarchy
• Make Antidote do something the bot is not allowed to do

fakepermissions grant @Co-Owner administrator

Permission names

These are the flags you can grant. They only affect Antidote command checks.

Permission	Typical Antidote use
administrator	All user command permission checks
ban_members	Ban / unban
kick_members	Kick
moderate_members	Timeout, mute, warn, history
manage_messages	Purge / delete messages
manage_nicknames	Nickname commands
manage_roles	Role management commands
manage_channels	Channel commands (some still check native per-channel perms)
manage_guild	Server management commands
manage_webhooks	Webhook commands
manage_expressions	Emoji / sticker commands
mute_members	Voice mute
deafen_members	Voice deafen
move_members	Move members in voice
mention_everyone	Commands that need mention everyone
view_audit_log	audit — paginated Discord audit log
view_guild_insights	Insights-related commands
external_emojis	External emoji commands
change_nickname	Changing their own nickname through the bot

Unknown names are rejected. Check fakepermissions in Discord for the live list.

What fake permissions do not do

• They do not change Discord role permissions.
• They do not let someone use Discord’s native ban, kick, timeout, or channel settings.
• They do not give the bot extra permissions. Antidote must already be allowed to ban, kick, and so on.
• They do not skip hierarchy. A moderator still cannot punish someone with a higher role.
• They do not unlock Fake Permissions setup. Only the real server owner can grant or reset.
• They do not apply on a server that is not premium.

Checklist

1. Staff roles in Discord have no Ban Members, Kick Members, Manage Channels, or Administrator.
2. Antidote’s role is high enough to moderate those staff and the people they punish.
3. Antidote itself has Ban Members, Kick Members, Moderate Members, Manage Messages, View Audit Log (for audit), and anything else you expect it to do.
4. Fake Permissions grants match the commands those roles should run.
5. Antinuke is on, so leftover native permissions still cannot raid.

Related

• Dashboard — Fake Permissions settings
• Antinuke — punish people who already have Discord permissions and abuse them
• Automod — automatic message punishments
• Premium — Server Premium unlocks this feature