Comparing an Authenticated User Experience with the Guest Experience

Comparing an Authenticated User Experience with the Guest Experience 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.

Support workflow

  1. Identify the exact frontend behavior or permission you need to verify.
  2. From Joomla Administrator, start QCUI for an eligible user who represents the affected account or ACL state.
  3. In the separate frontend tab, navigate to the specific menu, module, page, form, profile, membership, portal, or extension workflow under test.
  4. Record what is visible/allowed and compare it with the intended Joomla groups, access levels, menu/module assignments, or extension rules.
  5. End impersonation before making unrelated changes; after changing permissions/configuration, start a fresh or clearly controlled retest.

What to compare

For an Authenticated User Experience with the Guest Experience, compare the target user’s visible navigation and permitted actions with the intended Joomla user groups, access levels, menu/module assignments, and any extension-specific rules. QCUI shows the effective frontend result; it does not explain or override the underlying ACL decision.

Avoid false conclusions

Use a clean guest tab/session for the comparison so cached authenticated state does not contaminate the result; compare the same URL, language, and device conditions when possible.

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.