Permission tiers

kesarAI uses a two-tier permission model: Standard for everyday moderation, and AIfor commands that spend the server's point budget. Both tiers are assigned per-role through the moderation cog — Discord's native permissions are not consulted.

Two tiers

Every 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. /warn, /note, /timeout, /slowmode, /say, /transcript — the usual moderation kit.
• AI. /ask, /think, /summarise, /fallacy, /modadvice, /imagine, /edit.

Roles can hold either tier, both, or neither. There is no implicit inheritance — granting AI doesn't grant Standard, and vice versa.

Assigning mod roles

Use /modpermsto open the assignment grid. It's a button-driven UI: pick a role, then toggle Standard / AI on or off. Changes save immediately to the config database.

Tip. Most servers start by giving their full mod role both tiers, then create a separate "AI access" role that grants only the AI tier — letting trusted regulars use /ask without 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 configured via environment variables):

• /ai-limits — configure the point budget and per-command costs.
• /spy — screen new members against the cross-server spy database.
• /permrole — assign permanent (auto-restoring) roles and role bans.

These are deliberately not exposed to mods. Open an admin-only ticket with the bot owner if you need any of them adjusted.