Supported and Unsupported QCUI Impersonation Scenarios

Supported and Unsupported QCUI Impersonation Scenarios 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.

Supported

  • Super User support/admin inspecting an ordinary enabled frontend user.
  • Testing menus, modules, ACL, content, profiles, memberships, portals and extension-specific frontend experiences.
  • Separate admin/frontend tabs with a visible support-session banner.

Unsupported

  • Impersonating self or another Super User.
  • Blocked/reset-required/no-frontend-login targets.
  • Shared Sessions sites.
  • Background impersonation, master passwords, or password recovery.
  • Treating QCUI as a read-only preview—frontend actions can be real.

Current-product boundary

Supported and Unsupported QCUI Impersonation Scenarios reflects QCUI 1.0.03 as released: one System plugin, one token-lifetime setting, explicit Super-User initiation, no Scheduled Tasks, and no licensing/entitlement layer. Keep that boundary in mind when comparing older notes or assumptions from other QuantaCade products.

Current-product boundary

Supported and Unsupported QCUI Impersonation Scenarios reflects QCUI 1.0.03 as released: one System plugin, one token-lifetime setting, explicit Super-User initiation, no Scheduled Tasks, and no licensing/entitlement layer. Keep that boundary in mind when comparing older notes or assumptions from other QuantaCade products.

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.