1. Write down what failed and where
Was the bot assigning a role, changing a channel, sending a log, or moderating a member? Note the command, target channel and exact error. A bot can succeed in one channel and fail in another, so testing an unrelated command is not proof of access.
2. Match the permission to the operation
Assigning roles needs Manage Roles and the correct hierarchy. General channel edits such as slowmode use Manage Channels. Editing or deleting channel permission overwrites uses Manage Roles. Deleting other members’ messages uses Manage Messages. A timeout uses Moderate Members and also has target restrictions.
3. Inspect the effective channel permissions
Check the target channel’s category, role overrides and member-specific overrides for the bot. For messages, start with View Channel and Send Messages, then check Embed Links or Attach Files when used. A permission allowed on the server role can be restricted in a channel.
4. Separate user permissions from bot permissions
For acrO lock and unlock, both the invoking user and the bot need the required access in the target channel. Allowing the slash command in Discord Integrations does not override acrO’s runtime checks. Follow the message naming the missing permission rather than giving everyone broader access.
5. Change one setting and verify the result
Have an authorized administrator make the smallest relevant change, then retry in a test channel. Confirm that ordinary members still have the intended access. If a lock leaves someone able to write, inspect their other role or member overrides; Administrator bypasses channel overwrites.
Do not treat every Discord error as 50013. Missing Access (50001) and Unknown interaction (10062) are different errors. Copy the exact code when asking the bot’s support team for help.