Permission Boundaries

Server Manager requires live administrator/owner authorization. Stored web sessions, old approvals and Fork role grants do not substitute for the workflow’s current checks.

Bot capability

Fork must have the native permissions for each channel, role or access operation and sufficient role position. It cannot safely manage roles above itself merely because the requesting user is an Administrator.

Resource access

A private category needs correct overwrites and inheritance. Check @everyone, intended staff roles and other roles with broad access. Native Administrator can affect effective visibility; a single deny label does not tell the whole story.

Plan integrity

Approval is bound to the exact draft revision. Revising a plan, changing roles or losing access can invalidate the apply attempt. Do not attempt to bypass a rejected approval through an older route or session.

The public website’s example permission selectors are illustrative policies, not your guild’s configuration or default grants. See the broader Permission Model and Missing Permissions guide.