Role Access and Moderation Permissions

Ban and unban require Ban Members. Warning, unwarn, timeout, untimeout and moderation history require Moderate Members. Staff strike operations require Administrator. Fork’s command-role policy is an additional check.

Target boundaries

Member-targeting mutations that use the shared hierarchy guard refuse the server owner, the acting moderator and Fork itself. The target’s highest role must be below the moderator’s highest role unless the actor is the server owner. It must also be below Fork’s highest role.

Administrator does not move Fork’s role above the target. Channel overwrites and bot permissions may still block delivery or execution. Read-only record paths do not necessarily use the same target-mutation guard.

Configure role access

Complete setup and review Role Permissions in the dashboard. The grouped slash name maps to an underlying policy key: for example, mod ban uses ban, and mod strike add uses staffstrike. Do not create a second permission model based only on display labels.

See Permission model for setup fail-closed behavior, native Administrator bypass of the Fork matrix and the distinction between caller and bot authorization.