Block User for Joomla

Blocks a Joomla user account so they can no longer log in (sets the block flag). Use this for security lockouts, subscription expiry, or offboarding without deleting the account and audit history.

When the flow reaches this step, JOrchestrator executes Block User against your linked site or an external integration, using the field values you set on General and Design. Downstream steps can read the output payload fields defined for this node.

Block User is a action step in the Users group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.

Typical reasons teams add Block User to a flow:

• Lock accounts after repeated failed login attempts detected upstream
• Disable access when a subscription expires without deleting the user record
• Automate offboarding while preserving audit history (prefer over delete-user)

Common patterns on the canvas:

1. Trigger or Webhook → upstream steps → Block User → Send Email or CMS update
2. Scheduled trigger → Block User → Debug (while testing) → production action

Provide User ID or username on the Design tab; user id 1 (super user) cannot be blocked.

Pair with security flows on repeated login failures, or use unblock-user to restore access later.

The designer shows these tabs for this node:

After this step runs, later nodes can reference these fields using placeholders such as {{block_user.id}}.

Other steps in the same area of the palette:

• Create User (create-user) — Users
• Create User (wp-create-user) — Users
• Delete User (delete-user) — Users
• Delete User (wp-delete-user) — Users
• Get User (get-user) — Users