Two-person confirmation for inactivity reviews
Delegate manual inactivity cleanup duties to your moderation staff without giving every moderator personal Kick Members permission. Two independent authorized moderators must confirm each eligible inactive member before the kick is executed automatically.
CLNR✓ APP16:29Batch Kick Review
At a glance
This saved review contains 1 members who were eligible when it opened.
Approval rule
Owners and admins keep direct kick access. If moderator two-person confirmation is On, each target needs two different authorized moderators; the second approval triggers the kick automatically without a safety delay. Pre-kick DMs follow the server setting and include the configured reinvite link when available.
Next steps
Open the live review to verify current member status before choosing an action.
1. Faith
Profile: @Faith (faith3075)
Decay Score: 22.00 | Last Active: 14.09.2026
Review status
- @19Azrael90 (19azrael90): Confirm 1 of 2 for @Faith (faith3075). A different currently authorized person must confirm the same member before CLNR acts.
Example member details, dates, score, and approval state, not live data. Snooze and Exempt require admin access.
Independent Toggle Off by Default
Two-person approval is optional and off by default. It requires two other approvers for general removal requests and two different confirmations for eligible inactivity targets. With requests On and Two-person approval Off, one staff confirmation can kick eligible inactivity targets. Configure it via /removal config.
This option gives server owners the flexibility to allow trusted staff roles to review and confirm eligible inactive targets on review cards without granting individual moderators personal Discord Kick Members permissions.
CLNR✓ APP21:56🛡️ Staff Removal Approval settings
At a glance
🟢 Ready: Staff can start removal requests.
Current settings
- Removal staff role: @HighCommand
Also allows single-person staff Confirm for manual inactivity reviews when two-person approval is Off.
Require two authorized approvers for removal requests and eligible inactivity reviews. Turning both switches Off stops delegated Confirm.
How it works
- With two-person approval Off, each request needs one authorized reviewer other than its requester; that reviewer or an admin can execute after a 3-minute safety delay. With it On, two other authorized people must approve and an admin executes after the delay.
- Each staff member can record one destructive approval every 3 minutes. CLNR pauses after 5 removals within 15 minutes.
- Discord Administrators, CLNR admin-role members, and removal staff are protected targets. Remove the protected role first when removal is intentional.
- The removal staff role allows Confirm for eligible inactivity targets. With requests On and two-person approval Off, one authorized staff confirmation triggers the kick. With two-person approval On, two different authorized staff must confirm each target; the second triggers the kick. Neither mode adds a safety delay or extra Execute click. Turning both switches Off stops delegated inactivity Confirm. Owners and admins keep direct kick access. Moderator approval does not require personal Kick Members permission. With requests On and two-person approval Off, removal staff can individually select recovered candidates in the live review and accept a danger confirmation. Two-person mode keeps recovered candidates admin-only.
Changes save when selected. Choose a role or click an inline ON/OFF button to change its saved state. The removal role does not grant CLNR settings access.
Check readiness: /removal status
Both options are On in this example; each defaults to Off.
Eligible Inactivity Targets Only
Delegation is strictly restricted to currently eligible inactive members. It does not grant authority over protected or recovered candidates.
Currently Eligible Inactive Members
Delegated confirmation applies exclusively to members who pass all inactivity checks on review cards. Read more about fair member cleanup standards.
Recovered Candidates Admin-Only
With requests On and Two-person approval Off, removal staff can individually select recovered candidates and accept a danger confirmation for that recovery cycle. Two-person mode keeps recovered candidates admin-only.
No Extended Permissions Granted
Confirmation delegation grants removal staff no ability to adjust bot settings, snooze members, grant exemptions, or modify server inactivity rules.
Batch Approval Mechanics & Security Boundaries
To maintain efficiency during routine reviews, selecting a batch of members counts as a single approval action for the staff member's 3-minute cooldown timer. However, every single target member in that batch still requires two separate, distinct human approvers.
2 Distinct People Per Member
The same moderator cannot count twice toward a member's two-person threshold.
Security Invalidation
Disabling confirmation or changing the designated Removal Staff Role immediately invalidates all previously recorded unexecuted confirmations.
Batch & Cooldown Rules at a Glance
- 1. Batch Cooldown Credit: Confirming a batch of eligible members counts as 1 action for the moderator's 3-minute per-staff cooldown.
- 2. Individual 2-Person Requirement: Every target member must be confirmed by two distinct authorized staff members before execution.
- 3. Automatic Approval Cards: All approval state updates and failure notices remain attached directly to the original review card.
- 4. Guarded Rules: Review auto-kick guardrails for the separate automatic-kick activation workflow.
Comparing Inactivity Confirm vs. General Removal Approval
Understand how delegated inactivity confirmations differ from full general staff removal approvals.
Delegated Inactivity Confirm
Manual Inactivity Review Cards
- • Staff Count: Requires 2 distinct currently authorized moderators.
- • Safety Delay: No extra safety delay. Execution remains subject to current checks and the shared removal cap.
- • Execution Step: Automatic upon 2nd confirmation; no separate Execute click required.
- • Staff Discord Permission: Moderators do not need individual Discord Kick Members permission.
General Staff Removal Approval
Sensitive Kicks & Bans (/removal request)
- • Staff Count: Requires requester + 2 approvers (3 staff total).
- • Safety Delay: Mandatory 3-minute safety cooldown after 2nd approval.
- • Execution Step: Requires explicit final Execute removal click by an admin.
- • CLNR Permission: Requires bot Kick or Ban permission matching the requested action.
Automated Pre-Kick Recheck Pipeline
Before taking action upon receiving the second confirmation, CLNR rechecks all critical variables in real time. If any condition fails, the kick is halted and the error is reported on the review card.
Verifies both approvers remain authorized removal staff.
Checks exemptions, snoozes, hierarchy, and admin status.
Confirms candidate has not recovered active status.
Honors the server DM setting and member mute preferences. A changed reinvite link requires fresh confirmation.
Direct Admin Access Path
UnchangedServer owners, Discord Administrators, and configured CLNR admins retain their existing direct kick path and required Discord permissions regardless of whether delegated confirmation is enabled or disabled.
Direct Admin Rights Summary:
- Owners and admins retain direct kick access, subject to current review validity, permissions, and target checks.
- Direct kicks require standard Discord Kick Members permission.
- Delegated confirmation settings do not restrict owner or admin authority.
Learn how to explain inactivity rules to your moderation team.
Shared Removal Cap & Automatic Queue
Delegated inactivity confirmations count toward CLNR's shared removal velocity cap of 5 removals per 15 minutes across the entire server.
If a member receives two valid confirmations but is blocked strictly by the 15-minute removal limit, the target is held in an automatic recheck queue. CLNR retries automatically as capacity becomes available, rechecking both approvers, current access, review validity, and target eligibility before any kick.
Velocity Cap Rules
5 / 15-Min Shared- • Shared Pool: General staff removal requests and delegated inactivity confirmations share the 5 removals per 15-minute cap.
- • Automatic Queueing: Confirmed targets blocked only by the cap wait for an automatic recheck once the rate limit window resets.
- • Fresh Validation: When the queue clears, CLNR re-verifies member presence, eligibility, and exemptions before executing the delayed kick.
Emergency Kill Switch
Executing /removal off immediately stops new removal requests, destructive approvals, execution, and delegated inactivity Confirm. Deny and Cancel remain available.
An authorized admin can deliberately enable the required workflow again through /removal config.
Command Reference & Control Center
Click any command chip below to copy it directly to your clipboard for Discord. See full details on CLNR slash commands.
Configure Removal Settings
Configure removal features, assign the Removal Staff Role, and choose one or two approvers for requests and eligible inactivity reviews.
Check Removal Status
Displays current removal configuration, readiness, active staff role, and delegated inactivity confirmation status.
Emergency Kill Switch
Instantly disables removal request processing, approvals, and delegated confirmations across the server.
Show Full Server Config
Displays complete CLNR server configuration, including inactivity policies, roles, and safety settings.
Note: Confirm is an interactive button on review cards, not a separate slash subcommand.