AEM Publish with References can publish a page nobody approved

The page owner approved one release, but a related page appeared on the live site too. That is a governance incident, even when AEM behaved as configured. A practitioner request in Experience League describes exactly this anxiety: a referenced page may still be awaiting editorial approval.

Find the publication route

Start with the audit trail: who initiated publication, whether they used Quick Publish or Manage Publication, and which references were selected. Adobe's publishing documentation distinguishes these workflows. Reproduce on a nonproduction copy with the same reference graph. A reference shown in a dialog is not necessarily one the editor recognized as a separate page with a separate owner.

Make the dependency decision visible

Adobe's reference-publishing guidance explains how Manage Publication exposes published references for selection. Give the release reviewer a manifest of pages, assets and tags that will change, with owner and approval state. If a referenced page is not approved, deselect it where the workflow permits or postpone the release. Verify that omitting it will not break the intended page.

Test the guardrail as an editor

Run a release rehearsal with a deliberately unapproved referenced page. The acceptance test is whether an ordinary editor can identify and exclude it before publishing, and whether the audit record names every resulting live URL. Training alone is weak if the publishing UI makes dependencies easy to overlook.

Adovo’s view

Approval belongs to the release graph, not the button someone clicked. Every live dependency needs an owner who knew it would ship. If a publishing workflow cannot show that decision clearly, the workflow is unfinished.