> ## Documentation Index > Fetch the complete documentation index at: https://docs.bloombot.cloud/llms.txt > Use this file to discover all available pages before exploring further. # Permission errors > Work out why Bloom refused a command or could not act on a member, from the cheapest check to the most involved. Most refusals come down to one of four things. Work through them in order. ## Read the pronoun first Bloom always says whose permission is missing, and that points straight at the fix. | Bloom says | Meaning | Fix | | ------------------------------------ | ------------------------------ | --------------------------------------------------------------------------------------------------- | | *You need the following permissions* | You lack the user permission | Give the member the Discord permission, or a matching [fake permission](/security/fake-permissions) | | *I need the following permissions* | Bloom lacks the bot permission | Give Bloom's role that permission, and check the channel is not denying it | Confirm whoever is blocked actually holds the permission the command names. Administrators and the server owner pass every Bloom check. A channel override can deny a permission in one channel while the role grants it everywhere else. Bloom uses your effective permission in the channel you ran the command in, and its own in that same channel. Send Messages and Embed Links are the two that most often block a reply. If the permission is clearly present but the action still fails on one member, it is almost always hierarchy. Bloom, and the acting moderator, must have a higher top role than the target. Discord enforces this and no permission overrides it. Some commands are not permission-gated at all. `antinuke`, `staffroles`, and `fakepermissions` are limited to the server owner and anti-nuke admins. `hardban` and `antinuke setup` are owner-only. Never fix a permission problem by granting Administrator. It bypasses every check in the server, including the ones protecting you. Grant the specific permission, or use a [fake permission](/security/fake-permissions) to delegate just the Bloom command. ## Common cases Hierarchy. Bloom's role is at or below the target's highest role. Open **Server Settings → Roles** and drag Bloom's role above every role it needs to manage. Also hierarchy, on their side. Discord will not let anyone action a member whose highest role is above their own, no matter what permissions they hold. A channel override is denying Bloom Send Messages, Embed Links, or View Channel there. Check the channel's permission list for Bloom's role. Fake permissions satisfy Bloom's checks only. Anything Discord itself gates on that member's rights still requires the real permission. Modules appear only to members holding the matching permission. Getting in through a dashboard access role shows you only the modules for permissions you hold. See the [module matrix](/reference/permissions#dashboard-module-access). ## Related pages How the checks work, rather than how to fix them. The permission tables behind every check. Delegating Bloom commands without Discord permissions. Ask if none of the above explains it.