Excluding channels and roles from moderation

Not every channel benefits from Civora. The memes channel needs more leeway than your support channel; the mod-only channel doesn't need a bot reading staff conversations. Civora supports exclusions at both the channel and role level so you can shape its footprint to match how your community actually works.

Why excluding matters#

Without exclusions, Civora applies the same rules everywhere. That usually produces two kinds of friction:

• Annoying false positives in channels where the social contract is different. A "shitpost" channel has different language norms from #general; a private mod channel has different content norms from the public part of the server.
• Wasted attention on parts of the server where moderation is already handled (e.g., a staff channel where any issue is already being addressed in real time).

How to exclude a channel#

1. Open the server from the Servers page in the dashboard.
2. Switch to the Excluded channels tab.
3. Use the channel multi-select to add the channels you want Civora to skip.
4. Save. The exclusion takes effect immediately for new messages.

Excluded channels are skipped entirely — Civora doesn't run any of the six categories against them. Messages already moderated before the exclusion stay in their current state; Civora doesn't retroactively undelete or unflag anything when you change exclusions.

When to exclude a channel#

Reasonable cases:

• Memes / shitposting channels where the language norm is "anything goes within taste."
• Mod-only / staff channels where the people in the channel are trusted not to violate.
• Voice-text channels that exist only to support a voice room and rarely produce useful moderation signal ("okay I'm joining" / "be there in a sec").
• Roleplay or in-character channels where members deliberately play characters that say things the player wouldn't endorse.
• Bot-only channels (e.g., where another bot posts logs or game results). No human content means no moderation needed.

Unreasonable cases:

• A channel where mods are too busy to deal with mod issues. Usually means you need more moderation, not less.
• #general. Don't exclude your main channel. If #general feels like it needs to be excluded, your threshold tuning is wrong.

How to exclude a role#

Role exclusions are simpler: any user holding the excluded role bypasses Civora entirely on every channel.

1. Open the server, switch to the Excluded roles tab.
2. Use the role multi-select to add the roles you want to skip.
3. Save.

Useful for:

• Your moderator team. Civora shouldn't be flagging your own moderators' messages.
• Trusted long-term members. A "veteran" or "trusted" role for people who've been around for years.
• Verified content creators in fan communities (often the actual creator's account).

When NOT to exclude#

A few patterns where exclusion feels like the right tool but isn't:

• "Civora is too strict on this channel" → tune the category thresholds instead. Going from "active" to "totally absent" is a big swing.
• "This user keeps tripping Civora" → if it's one user, the issue is the user, not Civora. Have a mod conversation, or action them directly from the review queue or audit log.
• "This bot's messages keep getting moderated" → bots use their own user accounts; their role is usually the right exclusion target, but check that you're not also exempting human members who share that role.

How channel and role exclusions combine#

The two stack: if a message is in an excluded channel OR from a user with an excluded role, Civora skips it. Worth knowing when you're debugging "why didn't Civora catch this?" The Audit page shows what Civora processed; if a specific message doesn't appear at all, it was excluded.

What's next#

• Severity tuning — if you're excluding a lot, you might actually need to tune (Pro and Business).
• Reviewing flagged messages — the human side of automod.