Test configuration before activation
Global, customer and domain feature policies use inheritance with explicit enforced values. Create a draft, review the differences and choose representative customer content.
Open the isolated test workspace. Test edits are stored separately; customer drafts, media and publications remain unchanged. Complete opening, editing, responsive, saving and permission checks.
The checklist is your review attestation, not an automatic test suite. Activation requires a preview session, a real isolated test save and every checked test step. It rejects stale settings. Rollback creates another reviewable draft. Administrator support editing of a real customer page requires an explicit, audited switch.