Troubleshooting a Blocked Target User

Troubleshooting a Blocked Target User requires identifying whether the problem is in plugin visibility, target eligibility, the short-lived handoff, or the separate frontend session before changing configuration.

Diagnostic procedure

  1. Open Users → Manage and locate the target.
  2. Confirm the account is marked blocked.
  3. If policy permits, resolve the reason for the block and enable the account using normal Joomla administration.
  4. Start a brand-new QCUI handoff; old denied handoffs are not reusable.

Keep the layers separate

This is an intentional account-state denial. Resolve why Joomla marks the target blocked before testing any token or session behavior; QCUI should continue to refuse the account while block=1.

Information to preserve

Record the target username, Joomla blocked status, and whether the account is intentionally suspended. Passwords and handoff tokens are irrelevant to this denial.

When to escalate

If Troubleshooting a Blocked Target User persists after the documented layer is verified, stop creating repeated handoffs and preserve the exact error/context. A private support case should include version/state evidence but never passwords, session cookies, MFA secrets, or raw QCUI tokens.

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.