Understanding the Impersonation Started Audit Event

Understanding the Impersonation Started 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 started when the one-time token was consumed and the frontend identity switched. The row includes administrator/target IDs when known, UTC time, source IP, browser user-agent, and a short details message.

How to interpret it

A started row confirms the token was consumed and the frontend identity switch completed. It does not enumerate every page or action performed afterward.

Current UI boundary

QCUI has no Activity screen showing started sessions. Joomla and the tested component remain the sources for any detailed application-action history.

Privacy boundary

For Understanding the Impersonation Started 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 Started 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.