Private & Published

Private and Published mark the boundary between editable content and the public release. They do not collapse saving and publishing into one action: a saved revision can remain visible only in the edit tenant until an authorized publication updates the live site.

Inspect the Public state and Make Private boundary

Open the workflow popover and read the current state before acting. In the visible Public state, the panel explains live visibility and presents Make Private as a separate workflow action.

Private

Private content remains available to authenticated editors with permission in the edit tenant. It is not intentionally exposed as a public page, making it suitable for drafting, staging, review, or temporarily withdrawn information.

Published

Published content has a live release that visitors can reach through its public destination and connected navigation or listing surfaces. Later saved edits do not automatically replace that release; publish again only when the new revision is ready.

Make Private carefully

Make Private removes the public release boundary without deleting the editable content. Review inbound links, navigation, listings, parent/child destinations, and any campaign or form dependency before retracting a page.

Use staged review

Keep new work Private. Save meaningful revisions. Inspect the edit View at Desktop, Tablet, and Mobile. Verify copy, metadata, links, media alternatives, forms, focus, and touch behavior. Then choose page publication or a coordinated site release.

Common mistakes

Assuming Save publishes; checking only the editor canvas; making a parent Private without reviewing children; relying on dates instead of workflow state; or changing state without confirming the exact path and domain.

State checklist

Exact page confirmed. Edit and live domains distinguished. Current state read. Latest revision reviewed. Related navigation and listings checked. Correct release scope chosen. Live destination reserved for post-publication verification.

Next steps

Use Content Workflow for the review sequence and Publish a Site when several pages or global design surfaces must be released together.