Understanding QCUI Denial Audit Events

Understanding QCUI Denial Audit Events 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.

Recorded event

QCUI writes denied_* when QCUI refused Shared Sessions, unknown/invalid targets, or lost issuing-admin authority. The row includes administrator/target IDs when known, UTC time, source IP, browser user-agent, and a short details message.

How to interpret it

A denial row identifies the QCUI gate that refused an attempt. Use its action/details to investigate authorization, target eligibility, or Shared Sessions rather than treating it as a generic login failure.

Current UI boundary

Denials are stored internally; the administrator-facing workflow relies on the explicit Joomla error message rather than a separate QCUI audit-management screen.

Privacy boundary

For Understanding QCUI Denial Audit Events, 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.