Understanding QCUI Browser-Tab and Session Boundaries
Understanding QCUI Browser-Tab and Session Boundaries 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.
Boundary map
| Context | Identity/state |
|---|---|
| Original administrator tab | Existing authenticated Super User administrator session. |
| Handoff/new tab before consume | Transient one-time handoff page; not yet target session. |
| Impersonated frontend tab | Forked Joomla site session as target, with QCUI flags/banner. |
| After End impersonation | Forked site session as guest; original admin remains separate. |
| Banner position | Browser sessionStorage for current tab, not account/server preference. |
Shared Sessions
Joomla Shared Sessions would blur this map, so QCUI refuses to operate when that setting is enabled.
Current-product boundary
Understanding QCUI Browser-Tab and Session Boundaries 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
Understanding QCUI Browser-Tab and Session Boundaries 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.