Skip to content
Recued
Menu
← Back to recipes

Unban a Clerk user

by recued-core v1

Approval-gated Clerk user unban workflow for one user. It reads the user for context, then calls recued-core.clerk.user.unban for exactly that user. It does not create sessions or tokens, reset credentials, change MFA, mutate organization roles, delete users, or call arbitrary Clerk APIs.

How it works 5 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (5 steps)
normalized_user_id trim
Trim whitespace from setting user id
normalized_reason trim
Trim whitespace from setting reason
user_before ?
unban ?
card to_summary
Format results as a summary card
Settings 3 configurable

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.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Clerk connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

clerk clerkidentityunbanuser-lifecycleaccess-governanceapprovalpack:clerk

Details

5 steps 3 configurable settings recipe_id: unban-clerk-user