Recognizing That You Are Inside the Private Laboratory

QCUL adds persistent visible identity to the clone so an administrator is less likely to confuse a private test copy with the live site.

Laboratory identity cues

• Frontend and administrator pages show a private-laboratory banner.
• Page titles are prefixed with [LAB].
• QCUL applies a laboratory body class/favicon treatment.
• Opening QCUL inside the clone says to manage the laboratory from the live site.
• A specifically allowed return-to-production link leads back to production QCUL.

Why this matters

Human error is a major staging risk. Visual identity does not replace technical isolation, but it helps prevent an administrator from editing/testing the wrong environment or assuming a lab action changed production.

Stop if identity is missing

If the URL looks like a laboratory but the expected lab identity/runtime marker is absent, do not continue update testing. Return to production QCUL and refresh/repair the laboratory so its protection state is coherent.

Safety check before update testing

Before relying on Recognizing That You Are Inside the Private Laboratory, confirm the private copy still shows laboratory identity, its access gate works, and ordinary browsing stays inside the lab rather than silently using production. The cloned site contains production-derived data, so a laboratory that is not demonstrably isolated should be repaired or refreshed before any update rehearsal.

Community Discussion

Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.