Permissions and access levels
Who can press what, on Discord and on the web panel.
Every capability in the reference lists its permission policy. The policy strings map to everyday roles as follows:
| Policy | Meaning |
|---|---|
| anon | Public page, no sign-in needed. |
| dc_user | Any Discord user; works in DMs too (tickets). |
| guild_member | Member of the guild where the action happens (roster buttons). |
| guild_officer | Shot-caller or admin role holder, guild owner, or bot owner. Gated with Discord's Manage Server visibility. |
| session_user | Signed in on the web panel. |
| session_user+guild_member | Signed in and officer of that guild. |
| session_user+guild_admin | Signed in and admin-role holder of that guild. |
| oauth_bearer+discord_manage_guild | Discord-checked Manage Server during signup claim. |
| guild_entitlement | The guild's plan includes the feature (premium check). |
| app_admin | Bot owner only (allowlist, code generation, admin console). |
On Discord the officer check reads the per-guild settings you saved: the configured shot-caller/admin role ids, the guild owner, and the bot owner all pass. Role holders are resolved live, so removing a Discord role revokes access immediately.