Why use them
A moderator with real Ban Members can ban through Discord’s own interface, through any other bot, and through a script hitting the API directly. If that account is compromised or turns hostile, nothing in your server limits the damage. Give them a fake Ban Members instead and the picture changes: they can still run!ban, and every ban goes through Bloom, where it is logged with a case number and subject to your anti-nuke thresholds. Outside Bloom, Discord still sees an ordinary member with no ban rights.
What a fake permission does and does not do
Bloom still performs the action with its own permissions and role position, so Bloom needs the real permission even when the moderator does not.
Which permission does a command need
Run!help <command>. The reply has a Required Permissions field naming what the command checks, and that is the permission to grant.
Granting them
Owner or anti-nuke admin
Aliases:
fakeperms, fp, fakeperm.!fp grant <@role|@user> <permissions>grants one or more, comma or space separated.!fp remove <@role|@user> <permission>removes one.!fp clear <@role|@user>removes all of a target’s.!fp list <@role|@user>shows what a target has.!fp configlists every fake permission set in the server.!fp permslists the names you can grant.
Grant a role two permissions
Granted to Helper: Ban Members, Timeout Members. Names accept friendly aliases, so ban and ban_members do the same thing. The full list is in the Permission reference.
Recommended setups
Grant to a role rather than to individuals, so access follows the role.- Trainee
- Moderator
- Senior moderator
- Co-owner
Enough to handle chat problems, nothing that removes a member.
manage_messages— delete messages and purgemoderate_members— timeout members
What can receive them
- A member or a role. A role grant applies to everyone who has it.
- The @everyone role cannot receive fake permissions.
- Managed roles, meaning roles controlled by a bot or integration, cannot either.
Where they sit in a permission check
Bloom accepts a command if you are the server owner, hold Administrator, hold the real Discord permission, or hold a matching fake permission. Fake permissions are checked last, so they only matter for members who would otherwise be refused.Troubleshooting
Only the server owner and Antinuke admins can manage fake permissions
Only the server owner and Antinuke admins can manage fake permissions
You are an administrator, not the owner or an anti-nuke admin. Ask the server owner to run the command, or to add you as an anti-nuke admin.
The grant worked but the command still fails
The grant worked but the command still fails
Read which side Bloom names. “I need the following permissions” is about Bloom’s own access, which a fake permission never changes. Give Bloom’s role the real permission.
It works for the command but the action does nothing
It works for the command but the action does nothing
The member passed Bloom’s check, but the action still needs Bloom’s role to rank above the target. Move Bloom’s role up.
A booster or bot role cannot be granted anything
A booster or bot role cannot be granted anything
Managed roles and @everyone are excluded. Grant to a normal role, or to the members directly.
Related pages
Permissions and hierarchy
How Bloom decides who may run a command.
Permission reference
Every name you can grant, with its aliases.
Bans, kicks, and timeouts
The commands you are most likely to delegate.
Permission errors
Working out why a command was refused.