Required Discord Permissions

Fork checks more than one permission layer. Your authorization and the bot’s ability to perform an operation are different requirements.

Workflow	Member requirement	Bot requirement
Setup / Server Manager	Administrator, with live workflow checks	Permissions for the proposed operations and sufficient role position
Ban / unban	Ban Members plus Fork role access	Ban Members and valid hierarchy where applicable
Warnings / timeouts / moderation history	Moderate Members plus Fork role access	Timeout mutations need Moderate Members; records need available storage
AI-channel toggle	Manage Channels plus Fork role access	Channel visibility and message delivery access
Clear AI conversation	Manage Messages plus Fork role access	Access to the channel context store
AI-tool configuration / FAQ writes	Manage Server, with handler-specific checks	Available configuration storage

Check effective access

Inspect channel overwrites and the bot’s highest role, not only the permission checkbox. Member-targeting moderation protects the server owner, the caller and Fork; targets generally must be below both the moderator and bot.

Grant only the permissions needed for the selected workflow. Native Administrator can bypass Fork’s role matrix but does not make Fork’s own role position irrelevant. See Permission model and each command article for exact restrictions.