You're using an outdated browser

For a better experience, keep your browser up to date. Check here for the latest version.


Publish to a remote Confluence system

Roman Serazhiev

Roman Serazhiev Last update: Sep 24, 2018

If you have an internal Confluence in a secured environment and a separate public Confluence for your readers, you can publish to the public system using Scroll Versions on your secured authoring system and the Scroll Remote Publishing Endpoint installed on the public Confluence instance.

Confluence Application Links are used for communication between the two systems. You can publish to a completely new space in the remote Confluence, or update existing spaces. Whether you publish within the same Confluence system or to a remote Confluence system makes no difference for your readers: they won't see any Scroll Versions functionality in the target space and the space looks like a standard Confluence space.


To publish versions to a remote Confluence system, you have to meet multiple prerequisites:


You should only use OAuth (Impersonation) authentication to establish the application link – this method does not work with other authentication protocols.

Publish to remote system

Once the application link is set up correctly, you can select the remote system in the publishing options when publishing to a new or existing space.

Elements displayed in an unexpected way on the published page

After publishing, certain elements may not be displayed as expected in the remote instance. The behavior differs depending on whether Scroll Versions is installed in the remote instance:

Element Behavior with Scroll Versions installed Behavior without Scroll Versions
Page titles

The Scroll Page Title of source pages is published as the page title, and the permalink will be visible in the URL.

Prerequisite: Scroll Translations is not enabled in a master space.

If Scroll Versions' duplicate page title feature is activated in the source space, the permalink of pages is published rather than their title. We've documented a workaround here: VSN-3324 - currently there's not much we can do to improve this situation beside that.

Page keys Page keys are displayed in the remote space Page keys are not displayed in the target space
Scroll Pagetree macro Displayed as in the authoring space

An 'Unknown macro' message is displayed instead of the macro.

The scroll page tree macro should be converted to a standard Confluence page tree macro when published, we are tracking this behavior at VSN-3483

Scroll Metadata macro The metadata macro is published to the page with the same settings, but because the published page will have different metadata to the original (there will be no versions, no workflows, and no attributes on the published page), the macro will not display the same output as in the source page An 'Unknown macro' message is displayed instead of the macro
Excerpt Include+ macro Displayed as in the authoring space

An 'Unknown macro' message is displayed instead of the macro.

We are tracking this behavior at VSN-3493

Include+ macro Is converted to Confluence's standard Include macro, and displays content as expected
Gliffy and Draw.io diagrams Displayed as in the authoring space

An 'Unknown macro' message is displayed instead of the macro.

We are tracking this behavior at VSN-2013

We use cookies to create a secure and effective browsing experience for our website visitors and to understand how you use our site (i.e. Google Analytics). For more information: click here.