Publishing database health screen
Only Confluence administrators can open the database health screen. Everyone else sees 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 content goes | Space settings → Publishing → Setup tab (or the Settings section inside the Capable Publishing space page) |
Decide whether people can publish by hand, and whether they must add a comment | Space settings → Publishing → Setup tab |
Choose where published pages land and whether the tree is mirrored | Space settings → Publishing → Structure tab |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Enable publishing | Space settings → Publishing → Setup tab | Allows content from this space to be published to another space. |
Target space | Space settings → Publishing → Setup tab | Chooses where approved content is published. You need to be an administrator of that space. |
Allow manual publishing | Space settings → Publishing → Setup tab | Lets people publish from the page byline. |
#Worth knowing
Bulk publishing and the maintenance tools need space-administrator rights on both the source and the target space. Ordinary authors only get the per-page byline button.
"Restrict publish permissions" only has an effect when the Allowed publishers list has people in it. 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 turns manual publishing off and limits content types to pages, whereas a fresh space defaults to manual + automatic and pages + folders. After a reset, folders quietly stop being publishable from the byline until you edit the settings again.
Publishing sends no notifications of any kind. No email, no Slack, nothing. A failed publish shows only as a Failed badge, in the Failed and Invalid lists, and in the bulk audit log.
On an unlicensed site, Capable doesn't react to Confluence events: no status updates when a page is edited or moved, no publish-on-approval, and no automatic re-adding of the app to page restrictions. Manual publishing still works, so the problem is easy to miss.
#Related
How it actually behaves.
