Why Impersonation Sessions Should Be Ended When Testing Is Complete

Why Impersonation Sessions Should Be Ended When Testing Is Complete is a deliberate QCUI 1.0.03 behavior that protects administrator access, target-account safety, or the integrity of the one-time impersonation handoff.

Clean finish

End impersonation converts that frontend session to guest, clears QCUI flags/MFA state, adjusts the user-state cookie, and writes the ended audit event. Simply leaving a tab open keeps a support identity available until normal session expiration or another identity change.

Risk reduction

Promptly ending reduces accidental actions under the wrong customer identity and makes the support session’s lifecycle clearer.

Preferred habit

Treat End impersonation like closing an elevated shell: finish the defined check, end the elevated context, then return to ordinary administrator work.

Privacy boundary

For Why Impersonation Sessions Should Be Ended When Testing Is Complete, 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.