How it works
Capable Publishing copies pages and folders from one Confluence space (the source) into a different space (the target), and keeps a durable link between the original and its copy so the copy can be refreshed later. A space administrator turns it on for a space, picks the one target space, chooses where copies land and whether the page tree is mirrored, and from then on content reaches the target space in exactly three ways: someone clicks Publish, Republish or Update in the page byline; an approval on the page is approved and "Publish on approval" is switched on; or a space administrator runs
#In this section
Publishing byline panelShows the page's current publishing state and the buttons to act on it. The main button reads "Publish" the first time, "Republish" once a copy exists, and "Update" when the page is Outdated or Moved. Clicking it only queues a background joPublishing space pageThe 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 AudBulk publish progress panel and Audit LogWhile a bulk job runs, a progress panel shows pending / in progress / published / failed / skipped counts and offers a Cancel button. The Audit Log holds the per-item history and logs of past bulk runs.Publishing panel in Capable SearchSearch and report on publishing state across the site. Columns: Overview, Status, Approvers, Method, Publisher, Published at. Filters: Published (date), Status, Publisher, Approvers, Method, Direction (source page vs published copy). Sort:Publishing database health screenConfluence administrators only. Non-admins see a permission notice instead.Publish on approvalThe 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.What a publish actually copiesConfluence's own content-copy is called with attachments and labels included, and page restrictions, content properties and custom content excluded. Before the copy runs, the page body is scanned: a link to another page in the same source sWhat re-publishing doesThe existing target page is overwritten in place. A new version of that page, never a second copy. If the desired parent changed, the target page is then moved (folders are recreated or moved). If a publish comment was given it is written aPublishing foldersPublishing a folder also publishes what is inside it: once the folder exists in the target space the job walks its child pages and child folders (250 per query) and publishes each of them. In bulk runs folders are given a priority boost soPage statusesPublished; Outdated ("Page has been published but is out of date") when the source page is edited; Out of sync ("Page has been published but is out of sync") when the target page is edited by someone else; Moved when the source page is giveWho the published copy is written byThe copy is written into the target space by the app itself, not by the person publishing, so ordinary authors need no permission in the target space at all. Manual publishes are attributed as "Published by <name>", approval publishes as "Pcapable_never_publish labelA permanent per-page opt-out. Any publish attempt on a page carrying this label is recorded as Failed with the reason "Publishing disabled by label".
#Related
How it actually behaves.
