If checked Content Properties associated with other plugins will be published.

• only the properties with prefixes specified in the global app configuration by Confluence administrator are published

Page properties are attributes associated with a page usually defined by other apps. See the other app's configuration to determine the prefix of these properties.

Labels

If selected, labels are published on target pages, blog posts, and attachments.

• if a global sync-label has been set this will not be included

Match labels

Checking this option causes an exact copy of all labels from a draft page/blog post to be added to the published space page/blog post including any sync-label.

Any existing labels on the content in the published space are removed and replaced by the labels on the content in the draft space. 

Restrictions

If checked

• publish source page with any added page restrictions
• page restrictions in published space will be replaced

Scaffolding

If active (ServiceRocket Scaffolding app or macros enabled) and checked

• publish the scaffold data such as metadata

Note that only the latest version data is published.

Version Comments

Override Content

When publishing, the page history is not retained on the published content in the target space. If selected, no new versions are created. Page history is not kept

• if the page doesn't exist in published space, it will create that page with version 1.  Every time the page is published, that version will be replaced
• if the page already exists with multiple versions in the published space, it will just replace the most recent version with new content

Latest modification date

Checked by default

• on publishing, the modification date will be taken from the item (page/blog post/attachment) in the source draft space that is being published

Publish date will be unchecked if this option is chosen

Publish date

Unchecked by default

• if checked, for published pages, blog posts, and attachments the modification date will match the date the publishing occurred

Latest modification date will be unchecked if this option is chosen

Use sync-label

Option to utilize a sync-label to determine the content to be published

If checked

• only pages with the sync-label will be synchronized

If unchecked

• the sync-label will not be used to determine content to be synchronized

The sync-label is set by global administrator. The default value is syncme.

When using the sync-label the synchronization can be customized with the following options

• Publish content without the sync label will only copy content without the sync label
• Ignore sync-label for Blog Posts will copy all Blog Posts, Independent of sync-label
• Include child pages will publish child pages of a page with the sync-label

Publish content 
with the sync label

Only displayed if Use sync-label option is selected

Checked by default on choosing Use sync-label

If checked

• only pages with the sync-label will be synchronized
• Publish content without sync label radio button will be unchecked

If unchecked

• the sync-label will not be used to determine content to be synchronized
• Publish content without sync label radio button will be checked

The sync-label is set by global administrator.

Only displayed if Use sync-label option is selected

If checked

• only pages without the sync-label will be synchronized and pages with the sync-label will not
• Publish content with sync label radio button will be unchecked

If unchecked

• only pages with the sync-label will be synchronized
• Publish content with sync label radio button will be checked

The sync-label is set by global administrator.

Include child pages

Only displayed if Use sync-label option is selected

If checked, the sync-label synchronization will be applied to the page with a sync-label AND ALL its child pages.

Ignore sync-label 
for Blog Posts

Only displayed if Use sync-label option is selected

If selected, the sync-label as defined in Publishing Configuration in Confluence Admin is ignored for blog posts. All blog posts will be published (if set in the content filter) irrespective of the sync label.

If checked

• the sync-label is removed from all content in the source space after publishing is complete

This will occur whether or not the sync-label is used.

For example, let's say the sync-label is private and you add the label private to a draft space page. If this option is selected then after the space is published, the private label is removed from the draft space page.

Draft Watermark

Display Publishing Status Lozenge

Controls the display of the publishing status lozenge on content in the source space

If checked

• a lozenge for the current status of publishing synchronization is added on pages and blog posts in the source space

Recommend that this be disabled when using Comala Document Management to handle publishing which provides its own status lozenges.

Note: the behavior of the lozenge display on the target content is not affected by this option setting. The display of the publishing status lozenge on the target space content is dependent on the user permissions for the source content. 

Blog Posts

When checked - Blog Posts are included in the publish. If not checked, blog posts are ignored.

Pages

Top-level pages

Only displayed if Pages option is selected

If NOT checked

• don't publish top-level pages (such as the space homepage) and other orphan pages. If the space has multiple page trees each starting with a top-level page, each top-level page will not be published

If checked

• publish top-level pages in the source space including orphan pages

Always publish

Option to always publish content on a space publish action even if there are no updates on the source space content.

If NOT checked (default)

• only the elements of content that have changed will be updated in the published space

If checked 

• all space pages and blog posts are published even if no changes have been made
• ignores the manifest record (as seen on View Changes) that shows which pages and blog posts need publishing

Note that the View Changes report (the manifest record) may change if publishing options are changed.

Delete target space content (pages and blog posts)

Configuration option to delete target space content that is not currently in the source space when a space publish action occurs.

If selected

• content that exists in the public space but not in the source (draft) space  are deleted

If not selected (deafult)

• pages and blog posts that only exist in the public space are not deleted

out-of-sync pages are unaffected

A notification on View Changes shows pages that are out of sync: pages exist in the public space but not in the draft space.

Use final state

Publish the Comala Document Management app final state version of the content. A Comala Document Management app must be installed and a Comalatech workflow applied to the content.

If NOT checked

• current version of source content is published even if a Comalatech workflow is applied

If checked

• publish the version of the content corresponding to the Comala Document Management Family of apps workflow final state

Content will not be published that

• does not have a final state in the workflow
• does not yet have a final state version (no transition to the final state has taken place) 

When choosing to Publish a space, this option only publishes content with a new final/published version since the last time the space was published.

Only check this option if a Comalatech workflow is added and applied to content

Content will be published and synced on each transition to the workflow final state

If Single Page Publish is enabled, individual pages can be published, bypassing the workflow