Why QCUI Does Not Perform Hidden Background Impersonation

Why QCUI Does Not Perform Hidden Background Impersonation is a deliberate QCUI 1.0.03 behavior that protects administrator access, target-account safety, or the integrity of the one-time impersonation handoff.

Explicit interaction only

QCUI starts only after a Super User opens the visible administrator launcher, enters a username, and submits the start form. The frontend handoff opens separately and successful impersonation displays a visible banner.

No periodic/background switch

There is no Scheduled Task, remote service, or background job that silently changes a user identity. The plugin listens for explicit POST actions and injects the launcher/banner according to current session state.

Why this matters

Support staff should always know which account they are viewing. Hidden identity changes would defeat that operational safety goal.

Privacy boundary

For Why QCUI Does Not Perform Hidden Background Impersonation, 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.