QC User Impersonation Safe-Support Best-Practice Checklist

QC User Impersonation Safe-Support Best-Practice Checklist summarizes the current QCUI 1.0.03 rules and operational boundaries that are useful during administration and support.

Before

  • Confirm a defined support purpose.
  • Use a Super User account that is authorized for this work.
  • Choose the exact intended non-privileged username.
  • Confirm Shared Sessions is off.

During

  • Read the banner before state-changing actions.
  • Prefer observation and minimally invasive checks.
  • Coordinate with other staff/customer when concurrent actions matter.
  • Keep the administrator and target frontend contexts distinct.

After

  • Use End impersonation.
  • Confirm frontend is guest and administrator remains authenticated.
  • Record relevant support findings without copying passwords/tokens or unnecessary personal data.

Current-product boundary

QC User Impersonation Safe-Support Best-Practice Checklist reflects QCUI 1.0.03 as released: one System plugin, one token-lifetime setting, explicit Super-User initiation, no Scheduled Tasks, and no licensing/entitlement layer. Keep that boundary in mind when comparing older notes or assumptions from other QuantaCade products.

Current-product boundary

QC User Impersonation Safe-Support Best-Practice Checklist reflects QCUI 1.0.03 as released: one System plugin, one token-lifetime setting, explicit Super-User initiation, no Scheduled Tasks, and no licensing/entitlement layer. Keep that boundary in mind when comparing older notes or assumptions from other QuantaCade products.

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.