Why QCUI Does Not Provide a Customer-Facing Audit Log Screen

Why QCUI Does Not Provide a Customer-Facing Audit Log Screen is a deliberate QCUI 1.0.03 behavior that protects administrator access, target-account safety, or the integrity of the one-time impersonation handoff.

Current interface

QCUI is a System plugin with one setting and injected launcher/banner UI. There is no component dashboard or Audit tab in 1.0.03.

Why documentation must be precise

The audit table exists for internal evidence, but exposing it as if Joomla administrators can browse a built-in QCUI audit screen would invent a workflow that does not exist. If audit viewing becomes a future product feature, document it only after the released UI exists.

Today’s support approach

For ordinary support, use the visible QCUI messages plus Joomla/extension logs. Database audit inspection is an advanced administrative/database operation, not a required step to use impersonation.

Privacy boundary

For Why QCUI Does Not Provide a Customer-Facing Audit Log Screen, QCUI’s audit/session evidence should be handled as support/security data. Store or share only what your organization actually needs, keep raw handoff secrets out of tickets, and avoid copying unrelated customer information simply because the impersonated account can display it.

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.