security / access model

Permissions & hierarchy

Access is evaluated per guild. Discord permissions, the staff table, and the configured manager role each have a specific job.

01Everyone/help and /commands
02StaffRegistered staff, or members with Administrator. LOA, SLOA, warning views, tags, and tickets.
03ManagersStaff with the configured manager role. Staff lifecycle and tag catalog controls.
04AdministratorDiscord Administrator permission. Guild settings and manager fallback.

How checks work

staff(i) accepts a user in the guild's staff table or an Administrator. manager(i) accepts an Administrator or a member with the configured manager_role_id. Both checks are guild-specific.

Discord hierarchy still applies

Application access does not override Discord's role hierarchy. Kick, ban, nickname, and role actions can fail when the target is the server owner, the bot, or a member with an equal or higher role. Give the bot a role above members it must manage.