You are able to connect Stages with Confluence Cloud. A typical URL looks like:

https://example.atlassian.net

<cms-type name="confluencecloud">
    <cms-host ident="confluencecloud.ident.1" name="https://example.atlassian.net" displayName="Confluence Cloud Example">
        <cms-property name="user" value="user@example.com"/>
        <cms-property name="password" value="ATATT3xxxxxxxxxxx"/>
	<cms-property name="spacekey" value="SPACEKEY"/>       
    </cms-host>
</cms-type>

• cms-host ident*: This setting needs to be an arbitrary unique identifier for each cms host setting
• cms-host name*: The actual web address of the Confluence Cloud server without protocol (http/https) and port
• cms-host displayName*: The name of the Confluence Cloud server as it will be displayed in the Stages UI
• cms-property user*: Confluence Cloud user mail which will be used by Stages root user (system account) and for prefetching file metadata (revision numbers, checkin dates, …)
• cms-property password*: Confluence Cloud api key for Stages system account
• cms-property spacekey: Space-Identifier in which the documents are in

_{* Required settings}

Access to Confluence Cloud projects can be configured in Stages processes via “Management > File Management > Repositories”.

The following settings can be made:

• Name: The name of the repository as it will be displayed on other pages (e.g. in the file properties dialog)
• Host: Confluence Cloud host from config.xml (see ConfigurationSettings)
• Space Key: Name of the Confluence Cloud space
• Default lifecycle: Selects a lifecycle from the process metamodel as default for files from this repository.

The lifecycle state idents from the process metamodel (e.g. draft, review, released) must also be configured in the Confluence Cloud Space. For a correct color display it is recommended to disable custom status.

Version Handling: Each saved version of a Confluence page will create a new version, which will be shown in the document history.