Understanding the Impersonation Ended Audit Event

Understanding the Impersonation Ended Audit Event explains the current QCUI 1.0.03 behavior and how it affects a Super User who needs to inspect the Joomla frontend as an eligible user.

Recorded event

QCUI writes ended when the impersonated frontend was returned to guest. The row includes administrator/target IDs when known, UTC time, source IP, browser user-agent, and a short details message.

How to interpret it

An ended row confirms QCUI deliberately returned that impersonated frontend session to guest. It is distinct from the target user logging out their own other sessions.

Current UI boundary

QCUI records the lifecycle end internally but does not expose a session-history dashboard in 1.0.03.

Privacy boundary

For Understanding the Impersonation Ended Audit Event, QCUI’s audit/session evidence should be handled as support/security data. Store or share only what your organization actually needs, keep raw handoff secrets out of tickets, and avoid copying unrelated customer information simply because the impersonated account can display it.

Privacy boundary

For Understanding the Impersonation Ended Audit Event, QCUI’s audit/session evidence should be handled as support/security data. Store or share only what your organization actually needs, keep raw handoff secrets out of tickets, and avoid copying unrelated customer information simply because the impersonated account can display it.

Community Discussion

Want to compare support workflows, share practical tips, or discuss how you use this QCUI feature? Visit the QC User Impersonation Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.