Publish on approval
The only non-manual publish trigger. When an approval reaches Approved, the page is queued for publishing with method "Approval" and the approving users are recorded on the publish state and shown as "Approved by" in the Publishing byline. The space-level override is labelled "Publish on approval. Automatically publish content once approved. Overrides team and per-approval settings" and locks the per-approval checkbox on.
#Where to find it
Space settings → Approval → Overrides tab; also per approval team, and per approval in the approval byline options
#Where you do it
Task | Where |
|---|---|
Turn on publishing for a space and choose where conten | Space settings → Publishing → Setup tab (or the Settings section inside the Capable Publishing space page) |
Decide whether people can publish by hand, and whether | Space settings → Publishing → Setup tab |
Choose where published pages land and whether the tree | Space settings → Publishing → Structure tab |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Enable publishing | Space settings → Publishing → Setup tab | - |
Target space | Space settings → Publishing → Setup tab | - |
Allow manual publishing | Space settings → Publishing → Setup tab | - |
#Worth knowing
"Missing target" is only discovered on the next publish attempt, never when the target page is deleted, so that status can lag arbitrarily.
Recorded "missing links" are never shown to anyone. When a published page links to a page that has not been published, the link is left pointing at the source and the fact is stored and indexed, but no screen reads it. The only way to see them is a hand-written search query, and the field name differs between apps.
Page restrictions are not carried onto the copy, so a restricted source page becomes an unrestricted page in the target space. Separately, the app inserts its own app user into the SOURCE page's restrictions on every publish and whenever restrictions are edited in a publish-enabled space. Both are compliance-relevant and need approved wording, not just a footnote.
The status lists, dashboard counts and bulk-selection counts all read Confluence's search index, so freshly published or changed pages can be missing from them for a while. The byline shows a "Content not yet indexed" warning during that window.
Every catalogue list and dashboard count is filtered to pages only. Folders and blog posts never appear in Published, Unpublished, Outdated, Moved, Failed or Invalid, even though folders are published and tracked.
The claim that saving configuration requires administrator rights on both spaces is not true of the server. Saving is really only gated on source-space administration. The check that looks like a target-space check re-reads the source space. Target-space administration is a client-side Save-button disable that only fires when the target actually changes. Bulk publish is the one path that genuinely
#Related
How it actually behaves.
