Publishing database health screen
Confluence administrators only. Non-admins see a permission notice instead.
#Where to find it
Confluence settings → Capable (or Capable Publishing) → Publishing tab
#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
Bulk publishing and the maintenance tools require space-administrator rights on both the source and the target space. Ordinary authors only get the per-page byline button.
"Restrict publish permissions" only bites when the Allowed publishers list is non-empty. Switching it on and adding nobody leaves publishing open to everyone with edit rights.
In the Suite, the dedicated "Capable Publishing" byline is hidden on any page that has never been published, unless an administrator sets the space's Publishing visibility to "Always". The standalone Publishing app and the Approval app have no such condition.
A Reset to default does not restore the settings a brand-new space would have. It writes manual publishing off and content types limited to pages, whereas a fresh space defaults to manual + automatic and pages + folders. After a reset, folders silently stop being publishable from the byline until the configuration is edited again.
Publishing sends no notifications of any kind. No email, no Slack, nothing. A failed publish surfaces only as a Failed badge, in the Failed and Invalid lists, and in the bulk audit log.
On an unlicensed site none of the Confluence event listeners fire: no status updates on page edit or move, no publish-on-approval, and no automatic re-adding of the app to page restrictions. Manual publishing still works, so the failure is silent.
#Related
How it actually behaves.
