Safety controls
Moderation without blind spots
Kyvera combines immediate Discord actions with durable cases, evidence, and operator notes. Configure exclusions before enforcing filters across a busy community.Configure AutoMod
Add words or phrases that should be removed when they appear in member messages.
Block general links while allowing trusted domains needed by your community.
Set the message count, observation window, and timeout duration for rapid message floods.
Exclude trusted staff, integrations, or event roles from automatic filters.
Exclude channels where links or rapid posting are expected.
Choose when accumulated warnings should trigger timeout, kick, or ban escalation.
Moderation cases
- 1Action is recorded
Warnings, timeouts, kicks, bans, and AutoMod interventions create a numbered case.
- 2Evidence stays attached
Relevant violating message content and operational context are stored with the case. A live channel-message viewer is not required.
- 3Staff review the outcome
Use Moderation Cases to add internal notes, set a resolution, or mark the case appealed, resolved, or void.
Recommended rollout
- Start with exemptions and allowed domains.
- Enable one filter at a time and review the moderation case feed.
- Use realistic anti-spam windows so normal conversations are not punished.
- Keep warning escalation thresholds in ascending order.
- Confirm the Kyvera role can moderate the intended member roles.
- Use Command Access to limit destructive moderation commands to trusted staff.
Discord administrators and members above Kyvera in the role hierarchy cannot be moderated by the bot, regardless of the dashboard configuration.
Command Access can disable commands or limit where and by whom they are used.