Staff removal approvals for sensitive Discord decisions
Choose one or two independent approvers and keep a timed execution step before a sensitive kick or ban. With Two-person approval Off, one authorized reviewer other than the requester approves and that reviewer or an admin executes after the three-minute safety delay. With it On, two other people approve and an admin executes after the delay. This optional free workflow is off by default and separate from inactivity automation.
At a glance
- Status: Open
- Approvals: 2/2
- Expires: in 12 hours
Request details
- Target: @Bilgekdr (bilgepro10)
- Requester: @bivvo
- Action: Kick member
- Reason: inactivity
Optional details
- Ban message deletion: Not applicable
- Member DM: On
- Kick reinvite link: On
Decisions
- @Wulfrik420: Approved
- @Cobra: Approved
Activity
- 7 October 2026 at 22:26 · @bivvo: Request created
- 7 October 2026 at 22:26 · @bivvo: Requester decision rejected
- 8 October 2026 at 00:02 · @Wulfrik420: Approve
- 8 October 2026 at 00:22 · @Cobra: Approve
Safety delay
An admin can execute this approved request after 00:25:24 (10 hours ago), subject to the removal velocity cap.
Before CLNR acts
CLNR rechecks that the kill switch is off, staff authority, current membership, protected roles, hierarchy, the request deadline, the velocity cap, and its own permissions.
Screenshot example. Member IDs omitted for readability; shown settings and times are not defaults or live values.
The Four-Stage Guided Removal Process
Every destructive kick or ban request follows a strict four-stage pipeline ensuring multi-staff oversight, a safety cooldown, and a final deliberate execution step.
Private Guided Request
An authorized staff member launches /removal request. A private screen captures target, action (kick/ban), required reason, ban message deletion, and optional member DM, which is off by default. Only kick DMs can include the configured reinvite link. Kick and Ban independently require CLNR's corresponding permission; a failed optional DM does not prevent an otherwise valid action.
Independent Approvals
The card posts to the usable manual review channel or staff-channel fallback and initially mentions the removal staff role. Decisions and outcomes update that same card. One other authorized reviewer must press Approve with Two-person approval Off; with it On, two other people must approve. Each staff member has a 3-minute cooldown between approvals.
3-Minute Safety Delay
When the last required approval is recorded, CLNR starts a mandatory 3-minute safety cooldown. This buffer gives staff time to review the request, catch accidental approvals, or exercise a Denial or Cancel.
Execute the Approved Request
After the safety delay, the approving reviewer or an admin presses Execute with Two-person approval Off; with it On, the owner, a Discord Administrator, or a configured CLNR admin presses Execute removal. CLNR rechecks the required approvers' current access, target membership and eligibility, its own Kick Members or Ban Members permission, role hierarchy, and the kill switch before acting.
Who Participates & Access Boundaries
Participation requires authorization. Configure a dedicated Removal Staff Role via /removal config to delegate request and approval permissions without granting full server settings access.
Server Owner & Discord Administrators
Can create, approve, execute, or cancel requests without needing the Removal Staff role.
Configured CLNR Admins
Designated bot administrators have full participation and execution rights.
Removal Staff Role
Configured staff role can submit and approve requests. Does NOT grant bot settings access.
Automatic Target Protection
System immunity prevents misuse against protected server members
CLNR checks target eligibility when the request is created and again immediately before execution. Requests against protected targets are blocked automatically.
Server Owner, Discord Administrators, and configured CLNR Admins.
Members holding the configured Removal Staff Role or requester status.
Members possessing any inactivity-exempt role on the server.
CLNR itself, the original request creator, and missing members.
Rate Limits, Expiry & Emergency Kill Switch
Built-in checks and throughput limits reduce misuse and rapid-fire removals.
Shared Removal Rate Limit
CLNR enforces a server-wide hard limit of 5 executed staff-approved removals in any rolling 15-minute window. Even with valid approvals, general requests remain open and the authorized executor can retry after the rolling window clears. Delegated inactivity confirmations blocked only by the shared cap remain queued for an automatic recheck.
Request Expiry & Single Denial
Open removal requests expire after 24 hours, including approved requests that have not been executed. Furthermore, a single Deny vote by an authorized staff member other than the requester immediately closes the request.
Emergency Kill Switch
Executing /removal off instantly halts all new requests, approvals, execution, and delegated inactivity Confirm across the server. Deny and Cancel buttons remain functional so staff can clean up existing cards.
Removal Approval vs. Delegated Inactivity Confirm
CLNR provides two staff approval workflows suited for different operational needs.
Staff Removal Approval
Sensitive Manual Kicks & Bans
- • Participants: Requires one other reviewer with Two-person approval Off, or two other approvers with it On. The requester cannot approve their own request.
- • Cooldown: Enforces a 3-minute post-approval safety delay after the last required approval.
- • Execution: Requires an explicit final Execute removal click by the approving reviewer or an admin in single-person mode; an admin executes in two-person mode.
- • Scope: Targets specific members for manual moderation (Kick or Ban).
Delegated Inactivity Confirm
Manual Inactivity Review Cards
- • Participants: Requires one currently authorized moderator with requests On and Two-person approval Off, or two different moderators with it On, without requiring their personal Kick Members permission. Two-person approval is off by default and grants no Snooze, Exempt, or settings access. Disabling it or changing the removal staff role invalidates previous confirmations.
- • Cooldown: No extra safety delay once the required confirmation count is reached.
- • Execution: The required authorized confirmation count triggers execution automatically, subject to fresh checks and the shared cap.
- • Scope: Covers currently eligible inactivity members. Recovered candidates also support individual staff selection and danger confirmation in single-person mode; owners and admins keep their direct kick path and its required Discord permission.
Command Reference & Control Center
Click any command chip below to copy it directly to your clipboard for Discord.
Configure Removal Feature & Roles
Enable requests, choose the Removal Staff Role, and choose Two-person approval for requests and eligible inactivity reviews. 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. Request channels are configured separately through the existing channel settings.
Launch Private Request Screen
Opens a private screen to choose a current member, Kick or Ban, a required reason, and applicable message-deletion or optional DM choices.
View Current Setup & Readiness
Shows whether requests are enabled, readiness and blockers, the staff role, destination, bot permissions, and the separate inactivity Confirm setting.
List Open & Active Requests
Lists open requests with the target, action, current approval count, expiry, and links to their staff cards.
Emergency System Stop
Instantly disables request submission, approvals, and execution. Deny and Cancel options remain active to clear cards.