Recued
Menu
← Back to recipes

Ban a Clerk user

by recued-core v2 24 views

Use “Ban a Clerk user” in Recued. It runs the Clerk user ban workflow for one user with approval before changes are made.

How it works 8 steps

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 recued-core.clerk.user.read
Read user on clerk
◆ sessions_raw recued-core.clerk.session.search
Search session on clerk
◆ ban recued-core.clerk.user.ban
Ban user on clerk
■ sessions default
Apply default
■ session_count count
Count items in sessions
■ card to_summary
Format results as a summary card
▼
Output
summary card
Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

reason setting =
user id setting =

Uses (3 operations)

Pack operation Read user on clerk recued-core.clerk.user.read
Pack operation Search session on clerk recued-core.clerk.session.search
Pack operation Ban user on clerk recued-core.clerk.user.ban

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

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 clerkidentitybanuser-lifecycleaccess-governanceapprovalpack:clerk

Details

8 steps 2 configurable settings recipe_id: ban-user-clerk