Check readiness and publish
Publication creates a stable snapshot. New draft edits leave that snapshot unchanged until another explicit publication. Readiness explains missing required values and reference/media blockers.
How to use it
- Save the intended revision and inspect publishing readiness plus dependency impact.
- Resolve field and dependency blockers. If review is required, request approval for the saved revision.
- Use Publish when your current role permits it. Confirm the publication state and inspect your consuming website.
- Use Unpublish to take the public snapshot offline while retaining the draft; inspect Where used first.
Good practice
- Check current permissions, environment, language and publication state at the point of action.
Avoid
- Do not assume a disabled browser button is the only protection; backend checks remain authoritative.
Request and decide an editorial review
A workspace settings manager can make review optional or required, with an optional ordered list of stages. Approvals belong to an exact saved revision; publication stays separate.
How to use it
- In Workspace settings → Editorial, a settings manager enables Require approval before publishing. Saving policy requires a recent sign-in.
- Leave Review stages empty for single-step approval. Optionally add up to five named stages, check eligible reviewer roles and use Move up/down to order them, then save. Policy applies across workspace environments.
- An editor saves the intended text and submits a review request.
- An independent reviewer with current model/language review permission and an eligible stage role approves or requests changes. The editor shows progress, notes and the next stage. Every configured stage must approve in order.
- A publisher explicitly publishes the approved revision. Saving a newer version requires a new valid review when policy demands it.
Good practice
- Separate authoring, reviewing and publication responsibilities. Each stage needs an available independent approver in every relevant environment; one eligible person may review multiple stages. Custom-role plan limits and existing permissions still apply.
- Resubmit after changed revisions, schemas, policies or earlier approver access. Changes requested or cancellation restarts the chain on resubmission; schedules and releases recheck all required approvals.
Avoid
- Do not approve your own request or authored revision, select roles without approval grants, or treat earlier approvals as valid after edits or revoked access. Stage selection never grants additional permissions.
Schedule publication or unpublication
Schedules pin saved revisions and are executed by durable background jobs. Current permissions, dependencies and policy are checked again at execution.
How to use it
- Save the entry and open Schedule an action. Choose publication or unpublication, language and local date/time.
- Select the correct time zone. Resolve repeated clock times explicitly when required; invalid local times must be corrected.
- Review the resulting schedule, cancel or replace it when plans change, and inspect its outcome after the intended time.
Good practice
- Keep background workers running and inspect blocked/failed outcomes instead of assuming the clock guarantees success.
Avoid
- Editing an entry after scheduling does not update the pinned revision automatically; create a new valid schedule.
Publish or unpublish selected entries together
Collection checkboxes prepare up to 25 saved entries as a revision-pinned release. Selecting entries and preparing the review do not change public content.
How to use it
- Open a content collection in the intended workspace, environment and language. Check individual entries or Select this page. Only the current page is selected by that control; selected IDs and versions remain selected across pages, up to 25 total.
- Choose Clear selection to start over. Changing search, filters, sort, saved view, language, content type, workspace or environment clears the selection; leaving the collection also clears it. Entry titles remain links to the ordinary editor.
- Choose Review publication or Review unpublication. These actions require draft-read and the chosen model/language permission, plus publisher eligibility under the workspace review policy. Save editor changes first: bulk actions use saved revisions only.
- The prepared release shows action counts, languages and pinned versions. Open Pinned draft preview or the current editor for each entry. Use Where used to inspect paginated incoming saved-draft and published references you can read. Restricted usage is omitted; no dependency is automatically selected.
- Check readiness and resolve blockers: required values, valid entry approvals, saved versions and the final dependency graph must pass. A deleted or changed selected entry requires clearing/reselecting it; bulk actions never silently substitute a newer revision.
- Save readiness review, check the confirmation and Execute release now, or use the existing scheduling workflow. On small screens, Review and execute jumps to those controls. Execution rechecks permissions and all preconditions; either the complete batch commits or its publication changes roll back.
- Unpublication preserves drafts and history. Removing the default-language publication also makes the entry’s translations unavailable in delivery until it returns; saved translation snapshots remain. Shared fields and language fallback can affect other language responses when publishing. Consuming websites own cache/rebuild behavior.
Good practice
- Use a small, intentional selection in one language and inspect reference usage before removal. Choose a named release directly when a launch spans several models, languages or media.
Avoid
- Do not treat Select this page as Select all matching content, assume a readiness review grants entry approval, or assume retries select the latest revisions. Public/preview API credentials cannot execute bulk operations.
Coordinate a named release
A release groups up to 25 saved entry/translation/media actions into one publication transaction. Invalid final graphs roll back together.
How to use it
- Open Releases, create a named release and add authorized saved publication/unpublication actions.
- Review selected versions and remove/reselect changed items. Run Check readiness, then Save readiness review.
- Optionally capture a website impact comparison through your configured website renderer before deciding to publish.
- Confirm and execute now, or schedule the ready release. Inspect completed, blocked, retrying or failed outcomes.
Good practice
- Include all required dependency changes and review mixed publication/unpublication actions carefully.
Avoid
- Release readiness is not a substitute for required entry approvals, and website review never grants publishing authority.
Compare revisions, restore and inspect Activity
History preserves saved/publication revisions. Restore returns historical values to the editable draft; Activity records lifecycle operations for authorized workspace users.
How to use it
- Open entry history and inspect or compare revisions, keeping language and version in view.
- Choose Restore for the intended historical revision and resolve any current schema/validation issues.
- Review the restored draft; publish separately if it should become public.
- Open Activity to filter authorized lifecycle events by resource, action, actor or date. Workspace management categories remain restricted to Owner and Admin.
Good practice
- Use a descriptive editorial process around restores and compare the current published snapshot afterward.
Avoid
- Restoring is not a database rollback, and it does not undo external webhook side effects or automatically publish old content.