Safety foundations
Auto-Kick Guardrails that prioritize trust
CLNR keeps Auto-Kick predictable by default: 24-hour activation cooldowns, Safe Mode, and throughput caps reduce the risk and pace of unintended removals while giving staff visibility into activation and pauses.
Why these guardrails exist
Auto-Kick is optional and has a direct effect on membership. CLNR uses reviewed activation, current eligibility checks, staff alerts, and throughput caps to reduce the risk of mistakes. These safeguards do not guarantee that every removal is appropriate. Learn how CLNR evaluates inactivity in How CLNR Works and Discord Decay Score.
Misuse resistance
Mandatory 24-hour activation cooldowns and real-time permission checks block hasty or unauthorized execution.
Blast-radius control
Per-run, hourly, and daily throughput caps constrain total removals and automatically route excess candidates to staff review.
Full transparency
Staff alerts explain pending requests, cooldowns, pauses, and cap triggers. Losing the required staff channel or its permissions pauses automation until setup is restored and confirmed again.
Auto-Kick previews
Auto-Kick activation request. Dates, counts, and settings are examples, not live data or defaults.
The 24-Hour Cooldown Flow
- Activation Trigger: Executing the activation command places Auto-Kick into a pending state rather than enabling it immediately.
- Mandatory Delay: Confirmation becomes available only after a fixed 24-hour waiting window, giving the staff team time to review policy settings.
- 7-Day Expiration: If no eligible administrator confirms the request within 168 hours (7 days), the pending request expires and Auto-Kick stays off.
Two-Person Safeguards for Larger Guilds
- Tracked Roster Thresholds: Guilds tracking more than 100 managed members require two eligible admins for activation. Critical configuration changes are also risk-evaluated and can pause or block Auto-Kick and require fresh confirmation.
- Dual Confirmation: Activation requires confirmation from two distinct currently eligible admins: the server owner, a Discord Administrator, or a member with the configured CLNR admin role.
- Single-Admin Safeguard: If only one eligible admin exists, the same person can confirm again after the 48-hour single-admin cooldown; staff are notified that the fallback is being used.
Core protection layers in practice
Safe Mode for Unclear Impact
When CLNR cannot accurately compute affected member figures (for instance, while server scoring caches are rebuilding), confirmed Auto-Kick operates in Safe Mode using reduced execution caps. When the unavailable estimate is due to a rebuilding cache, confirmed Auto-Kick remains capped at 1 per run, 2 per hour, and 5 per day until an impact estimate clears. Missing setup or permissions blocks automation instead of allowing this fallback.
Throughput Caps & Manual Review Fallback
Auto-Kick execution is throttled across UTC-aligned hour/day windows and a per-run cap: per run, per UTC hour, and per UTC day. When any throughput cap is reached during an automated run, Auto-Kick pauses execution and routes remaining candidates into manual staff review queues. Use live manual review to check current candidates. Read more about review workflows in Fair Discord Member Cleanup.
Optional Compatibility Limit (auto_kick_daily_limit)
Server administrators can configure an optional compatibility limit ranging from 1 to 200 using /config set auto_kick_daily_limit. This setting is designed for servers that operate secondary anti-raid or audit security bots requiring low removal rates.
Effective Per-Run Limit = min(Built-in Per-Run Limit, Configured Compatibility Limit)
Effective Hourly Limit = min(Built-in Hourly Limit, Configured Compatibility Limit)
Effective Daily Limit = min(Built-in Daily Limit, Configured Compatibility Limit)
Mandatory Rule: The configured limit can only lower effective execution caps; it can never override or raise CLNR's built-in safety ceilings.
Real-Time Action-Time Eligibility Checks
Current authorization is checked when confirmation executes. Member eligibility, CLNR permissions, and role hierarchy are checked again before a kick. If an administrator loses Server Owner, Administrator, or configured CLNR admin role privileges during the 24-hour cooldown period, their pending confirmation attempt will be rejected automatically.
Related commands
Manage Auto-Kick guardrails directly in Discord using official slash commands. Explore all options in the Commands Directory.
/config show
Admin Only
Displays complete server setup, Safety Summary, configured compatibility limit, and effective execution caps.
/config set auto_kick_daily_limit <1-200>
Admin Only
Sets a custom compatibility limit (1 to 200) that lowers per-run, hourly, and daily removal caps.
/config remove auto_kick_daily_limit
Admin Only
Removes the custom compatibility limit and restores default CLNR built-in guardrails.
Workflow comparison matrix
CLNR maintains strictly isolated authorization models for different moderation workflows. Never confuse or merge these distinct safety processes:
| Feature Workflow | Primary Purpose | Required Approvers | Safety Cooldown & Execution |
|---|---|---|---|
|
Auto-Kick Guardrails
This Feature |
Automated inactivity cleanup settings and activation protection. | 1 eligible admin at up to 100 tracked members; 2 above 100, with the single-admin fallback described above. | 24-hour mandatory activation cooldown; 7-day expiration; UTC-aligned throughput caps. |
| Staff Removal Approval | Staff-requested general kicks or bans of current members, separate from inactivity automation. | 1 requester + 1 or 2 independent approvers, according to settings. | 3-minute mandatory safety delay before an approving reviewer or admin executes. |
| Delegated Inactivity Confirmation | Two authorized moderators confirm each currently eligible inactivity target; recovered candidates keep their separate admin-only path. | 2 Moderators confirming the specific target. | The second confirmation triggers the kick without an extra safety delay or Execute click, subject to current checks, cooldowns, and removal caps. |
Operational expectations
These guardrails do not take away staff control. They introduce structured friction only where necessary so administrators can catch mistakes early, maintain community trust, and review policies safely. For plan details, visit CLNR Pricing or read our Privacy Policy.
What stays the same
- Manual review queues remain available for edge cases.
- Staff alerts and configuration history explain state changes, subject to Discord delivery and channel access.
- Confirmed Auto-Kick can run only while setup, risk, permission, eligibility, and cap checks allow it.
What changes
- Activation requires an explicit 24-hour pending confirmation state.
- Throughput caps and Safe Mode automatically throttle high-risk runs.
- Guilds with more than 100 tracked members require two eligible admins, with the documented single-admin fallback.