Publishing space page
The reporting and management hub for a space. Sections: Getting started (a dismissible onboarding panel), Dashboard, a Pages group containing Published / Unpublished / Outdated / Moved / Failed / Invalid lists, a Manage group containing Audit Log and Settings, and an About group containing Roadmap.
#Where to find it
Space → Capable Publishing (standalone app) or Capable → Publishing (Suite / Approval app)
#ImportantDetail
The Settings section embeds the full four-tab space settings screen and is shown only to administrators of the source space. It is a second entry point to the same settings you reach from Confluence space settings. On the global (site-level) Publishing page the Invalid list, Audit Log and Settings sections are hidden; only Getting started, Dashboard, the five status lists and Roadmap appear.
#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
There is no scheduled or timed publishing. Nothing anywhere schedules a publish for a particular time. Scheduling is an unbuilt future idea.
The only non-manual source is Approval. Turning "Allow manual publishing" off therefore leaves approval-triggered publishing as the sole route into the target space.
"Allow manual publishing" reads Off in the settings screen before your first save, but the value actually stored for an untouched space is manual + automatic. Saving the form writes what the screen showed, silently turning manual publishing off.
"Save without rebuild" does not prevent a rebuild. The server starts one whenever the saved configuration changes the hierarchy mode, parent page, homepage inclusion or target space on an already-enabled space, regardless of which button was pressed.
Blog posts can effectively never be published. The code supports the type and a blog post can in principle be published one at a time, but bulk publish and Full Sync exclude them explicitly, and the byline button is hidden on them by the space's content-type setting, which has no control anywhere in the app. Blog-post edits are also never detected, so a published blog post can never go Outdated.
Approval-triggered publishing fails on any page whose parent is not already published, when hierarchy is preserved. Only manual publishes automatically publish the missing ancestors. The page just shows Failed with "Parent page is not published and could not be published".
#Related
How it actually behaves.
