Permission tiers
kesarAI uses a two-tier permission model: Standard for everyday utility commands, and AI for AI commands, which draw from each person's AI battery. Both tiers are granted to roles or members with /tier setup. The enforcement commands (ban, kick, mute and the rest) sit one level finer, in a per-role mod-permission grid. Discord's native permissions are not consulted for gated commands; Administrator always passes.
Two tiers
Every tier-gated command lives in exactly one tier. The split is about cost, not authority: AI commands can rack up real API spend if abused, so they get their own gate.
- Standard.
/say,/transcript,/afk,/embed,/userinfo,/serverinfo,/triviaand/trivialeaderboard. - AI.
ksrand/ai ask,/ai think,/ai summarise,/ai fallacy,/ai modadvice, and/imagine//edit.
Roles can hold either tier, both, or neither. There is no implicit inheritance — granting AI doesn't grant Standard, and vice versa.
Standard is open to everyone until you restrict it in /tier setup. AI is closed until you grant it (or pick Everyone in /quicksetup). In DMs there are no tiers.
The enforcement commands are not tier-gated. /ban, /kick, /mute / /unmute, /purge, /slowuser, the verify / quarantine pairs (/v, /unv, /q, /unq) and /roleadd / /roleremove each check their own mod permission (ban, kick, mute, purge, slowuser, verify, quarantine, role), set per role. /modai has its own permission gate too (mod_ai, separate from the Standard / AI tiers).
One overlap to call out: /roleadd and /roleremove are gated by the role mod permission, but dangerous-role grants are additionally gated by antinuke. A mod with that permission who tries to grant a role carrying administrator or any other Tier 3 permission gets an ephemeral denial unless they sit on the antinuke whitelist. See the antinuke caller-side gate for the full list of role commands that enforce this.
Assigning mod roles
Tiers are granted with /tier setup. The mod permissions are set with /modpanel — it opens a button-driven UI where you pick a role and toggle each permission (ban, kick, mute, purge, role, verify, quarantine, slowuser, roleban, perm_role, mod_ai, and more) on or off. Changes save immediately to the config database.
If you just want to read the current assignment without changing anything, run /modperms. It prints a summary of which roles have which mod permissions, no UI.
Tip. Most servers start by giving their full mod role the AI tier and the mod permissions it needs, then create a separate “AI access” role that grants only the AI tier — letting trusted regulars use
ksrwithout giving them ban-hammer access.
Owner-only commands
A small handful of commands bypass the tier system entirely and are locked to the bot owner (and any additional owner IDs in BOT_ADDITIONAL_OWNER_IDS):
/ailimits— configure the AI battery: size, refill time, the optional low-power mode, image allowance and per-user boosts and credits./permrolepersist— whether a server's permanent-role data survives the bot leaving.
The rest of the permanent-role commands (/permrole, /unpermrole, /permrolelist, /permrolecheck) are not owner-only: they use the perm_role mod permission, and the role-ban commands (/roleban, /unroleban, /rolebanlist) use roleban.
The owner-only ones are deliberately not exposed to mods. If you need an owner-only setting changed on your server, contact the bot owner through the support server.
