QCUI Database Table Reference
QCUI Database Table Reference summarizes the current QCUI 1.0.03 rules and operational boundaries that are useful during administration and support.
| Data | Lifecycle |
|---|---|
| Handoff token row | Stores hash, admin/target IDs, created/expires timestamps and used timestamp. Expired rows older than 24 hours are opportunistically cleaned when a new handoff is issued. |
| Audit row | Stores action, administrator ID, target ID, UTC creation time, IP address, user agent and a short details field. |
| Frontend session flags | Stored only in the impersonated Joomla session and cleared when ending or when the active identity no longer matches the expected target. |
| Banner position | Stored in browser sessionStorage for the current tab/session; it is not a server-side preference. |
Ownership
Both dedicated tables use the active Joomla prefix and the qcloginasuser internal identity. Joomla uninstall SQL drops both. Joomla’s own users/sessions tables remain Joomla-owned; QCUI only interacts with session metadata during targeted identity switching.
Current-product boundary
QCUI Database Table Reference 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.