Information to Collect Before Requesting QCUI Support

Information to Collect Before Requesting QCUI Support 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.

Collect

• Joomla version and QCUI version 1.0.03 (or actual installed version).
• Exact message and whether it appeared in Administrator, handoff page, or frontend.
• Whether Joomla Shared Sessions is enabled.
• Plugin enabled/disabled state and configured token lifetime.
• Target eligibility: exists, not self, not Super User, not blocked/reset-required, frontend login allowed.
• Whether the administrator remained signed in and whether QCUI CSS/JS loaded when UI was involved.

Do not collect

Do not send customer passwords, MFA secrets, session cookies, or raw handoff tokens. Those are unnecessary for QCUI support and may create a security incident.

Useful privacy practice

Share screenshots/logs privately and redact unrelated customer data visible in the impersonated frontend.

Current-product boundary

Information to Collect Before Requesting QCUI Support 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.