User Logout is a Trigger in Joomla Events › User Events. When a user logs out (front end or admin).
User Logout is a Trigger in Joomla Events › User Events. When a user logs out (front end or admin).
Session is destroyed or rotated; use for cleanup of user-specific caches or external token revocation.
Each run also includes who was logged in at the time and what kind of item was involved — see audit_user and audit_type in Payload Fields below.
This trigger is active when Platform Events are turned on in Joomla (System → JOrchestrator) and matching flows are set to Active.
When this trigger fires, JOrchestrator starts the flow and passes the incoming event or request data to the next connected step. Configure filtering, payload shape, and security on the Design tab.
User Logout is a trigger in the Joomla Events › User Events group. Triggers start a flow. They listen for an external signal — a CMS event, inbound HTTP call, payment notification, or schedule — and pass the incoming data to the first downstream step.
Typical reasons teams add User Logout to a flow:
UserLogoutWhen a user logs out (front end or admin).
Common patterns on the canvas:
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| Design | Trigger configuration and payload schema |
These fields are managed by the designer or runtime — you do not type into them directly:
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
_nodeId | Node ID | node-id | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.
After this step runs, later nodes can reference these fields using placeholders such as {{user_logout.subject.id}}.
| Field key | Type | Description |
|---|---|---|
subject.id | number | Nested field "subject.id" from this node's output payload. |
subject.username | string | Nested field "subject.username" from this node's output payload. |
subject.email | string | Nested field "subject.email" from this node's output payload. |
subject.name | string | Nested field "subject.name" from this node's output payload. |
options.clientid | number | Nested field "options.clientid" from this node's output payload. |
options.timeout | number | Nested field "options.timeout" from this node's output payload. |
audit_user.id | number | Nested field "audit_user.id" from this node's output payload. |
audit_user.username | string | Nested field "audit_user.username" from this node's output payload. |
audit_user.email | string | Nested field "audit_user.email" from this node's output payload. |
audit_user.name | string | Nested field "audit_user.name" from this node's output payload. |
audit_user.guest | boolean | Nested field "audit_user.guest" from this node's output payload. |
audit_user.client | string | Nested field "audit_user.client" from this node's output payload. |
audit_type | string | What kind of item triggered the event — for example article, category, or user. |
Other steps in the same area of the palette:
event-onUserAfterDelete) — Joomla Events › User Eventsevent-onUserAfterLogin) — Joomla Events › User Eventsevent-onUserAfterSave) — Joomla Events › User Eventsevent-onUserAuthenticate) — Joomla Events › User Eventsevent-onUserAuthorisation) — Joomla Events › User Events