Protecting Sensitive Customer Data Visible During Impersonation

Protecting Sensitive Customer Data Visible During Impersonation 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.

You may see real customer data

Because QCUI creates a real frontend identity session, the support tab can display whatever that target is legitimately allowed to see. That may include profile information, memberships, orders, tickets, private content, or extension-specific account data.

Operational safeguards

• Use impersonation only for a defined support purpose.
• Minimize viewing/copying of unrelated personal information.
• Do not post screenshots or handoff URLs/tokens publicly.
• End the support session when the task is complete.
• Follow your organization’s access, retention, and privacy policies.

QCUI’s role

QCUI controls how the support session is authorized and identified; it cannot decide whether every third-party page contains sensitive data. That remains an administrative responsibility.

Privacy boundary

For Protecting Sensitive Customer Data Visible During Impersonation, 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.