How QCUI Keeps the Launcher Available with a Custom Administrator Template

How QCUI Keeps the Launcher Available with a Custom Administrator Template describes a current QCUI 1.0.03 implementation detail that matters when you are validating security, session isolation, or support behavior.

Atum-first, template-safe fallback

QCUI first looks for Atum’s .header-items marker. When it exists, the launcher is inserted as a normal header item. When it does not exist, QCUI appends a fallback wrapper before </body> and fixes it near the top-right.

Popup clipping protection

The popup is moved under document.body when opened so transformed/overflowing header ancestors do not clip or resize it. JavaScript positions it relative to the trigger and keeps it inside the viewport.

No template override required

If a custom template still conflicts, fix the CSS/JavaScript conflict or CSP/optimization rule. Do not hard-code QCUI markup into the template, because the plugin already supplies the launcher.

Operational context

For How QCUI Keeps the Launcher Available with a Custom Administrator Template, 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.