Understanding That Frontend Actions Performed During Impersonation Are Real

Understanding That Frontend Actions Performed During Impersonation Are Real 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.

Not a preview mode

QCUI changes the active frontend identity; it does not wrap the site in a fake preview. A save, purchase, profile change, message, workflow submission, or extension-specific action can affect production data exactly as if that frontend identity performed it.

Safer testing

• Inspect visibility/navigation first.
• Use non-destructive test accounts when feasible.
• Avoid financial, communication, deletion, or irreversible actions unless explicitly required.
• Record changes you make so support work is auditable operationally.

End promptly

When the observation is complete, use End impersonation rather than leaving a privileged support tab active.

Session-safety check

After working with Understanding That Frontend Actions Performed During Impersonation Are Real, verify the identities explicitly: the support frontend should show the expected target while active, End impersonation should make that frontend guest, and the original administrator tab should remain the authenticated Super User. Any result that collapses those identities together should be investigated before further use.

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.