Understanding the QCUI Product Name, Plugin Name, and Internal Element
Understanding the QCUI Product Name, Plugin Name, and Internal Element 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.
Three names you may encounter
| Context | Name |
|---|---|
| Product/documentation | QC User Impersonation (QCUI) |
| Joomla Plugin Manager | System - QC User Impersonation |
| Internal Joomla element/table prefix | qcloginasuser / #__qcloginasuser_* |
Why the internal name is retained
The earlier internal element is intentionally preserved so Joomla upgrades replace the existing plugin instead of creating a duplicate under a renamed element. The public product name can be clearer while the technical identity remains stable for update continuity.
Support tip
When diagnosing files or database tables, expect qcloginasuser. When guiding administrators in Joomla, use the visible plugin name System - QC User Impersonation.
Operational context
For Understanding the QCUI Product Name, Plugin Name, and Internal Element, remember that QCUI has no separate component dashboard or remote authorization service. The System plugin owns the launcher/handoff/banner behavior locally inside Joomla. If what you see differs from these instructions, verify the installed plugin version and active Joomla template/session configuration before assuming another QCUI screen or service exists.
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.