Ban a Clerk user
Approval-gated Clerk user ban workflow for one user. It reads the user and active sessions for context, then calls recued-core.clerk.user.ban for exactly that user. It does not delete users, reset credentials, change MFA, revoke sessions or tokens, mutate organization roles, or call arbitrary Clerk APIs.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (8 steps)
normalized_user_id
trim
Trim whitespace from setting user id
normalized_reason
trim
Trim whitespace from setting reason
user_before
?
sessions_raw
?
ban
?
sessions
default
Apply default
session_count
count
Count items in sessions
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
clerk
setting
=
reason
setting
=
user id
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.