Remote-space publishing allows you to edit content on a local Confluence Server or Data Center, and then publish it to a remote Confluence Cloud, Server or Data Center instance.

The Comala Remote Publishing for Comala Document Management app must be installed on the source instance to enable remote-space publishing. 

Remote space publishing is triggered by an action macro, {remotepublish-page} used in a {trigger} added to the workflow.

  • the trigger can be set for different events.
  • the final=true parameter is not necessary for remote-space publishing, all the work is done by the {remotepublish-page} macro

The app also installs the {remoteremove-page} macro. This macro can be used in a  {trigger} for example when the content becomes obsolete and needs to be removed from the remote published content.

Set up remote space publishing

Once the Remote Publishing app is installed there are three steps to set up remote space publishing:

  • set-up the remote Confluence instance space where the content will be published to and add a user account with user permissions to view, add, and delete content in the space for the published content
  • set-up the local Confluence instance in the space tools Remote Publishing tab
  • update your workflow to trigger the publishing process

When content is published into this remote space it will appear to be authored and edited by the user you have set up.

For remote publishing to work, the server hosting the local Confluence instance must be able to access the remote instance.

The remote instance can be a server or a Cloud instance.

Using a Cloud instance as the remote instance

If a Cloud instance is used as the remote instance then you will need to configure an API token in the user account Atlassian administration.

The API token needed for the user password field needs to be requested by the user who will appear to publish the articles.

Remote Space Publishing




See also