Immunity (immunerole / immuneuser)

Use these commands to mark trusted roles or specific users as immune from AI moderation. Both require Manage Server.

#What "immune" means

When a user is immune (either directly or via a role they hold):

Their messages in moderated channels are skipped before any AI call. No screening, no judging, no cost.
Manual @mention scans still check their messages, and a violation may still be flagged in the log channel — but no action is applied and no DM is sent.
They count as immune even if they're the target of a manual mention scan, not just the author.

This makes immunity a hard skip rather than a soft "the bot will probably leave them alone" — useful for staff, bots, or anyone whose conduct you handle yourself.

#`/immunerole`

/immunerole add role:@Mods
/immunerole remove role:@Mods
/immunerole list

Any member who has at least one immune role is treated as immune. Most servers add their @Mod, @Admin, and @Helper roles here.

#`/immuneuser`

/immuneuser add user:@TrustedFriend
/immuneuser remove user:@TrustedFriend
/immuneuser list

Per-user immunity, independent of roles. Useful for the rare individual exception (e.g. an alt account, a partner-server bot you've added).

#Common patterns

All staff immune: /immunerole add role:@Staff. Most servers do this.
Bots immune: the bot already ignores other bots automatically — no action needed.
Trial-mod period: make a @Trial Mod role non-immune so the bot still applies to them; immune them once they're trusted.
Channel allowlist instead of immunity: if you only want the bot in one channel, just use /setmodchannels with that one channel rather than making everyone else immune.

#What immune users still see

If an immune user breaks a rule and the bot would have acted, the log embed shows:

🛡️ User is immune — no action applied

…with the rule, severity, and reasoning. This way your moderators still see what's happening and can intervene manually if they want to.