Scroll Remote Publishing Endpoint for Cloud
Description
Environment
None
Activity
Show:

Tobias Sernatinger November 19, 2018 at 3:44 PM
Are there any news for this feature request?
Not being able to publish from a (private) Confluence Server to (public) Confluence Cloud is a showstopper for us.
The feature would be much appreciated. Thanks in advance.
Michael March 20, 2017 at 4:22 PM
We would appreciate to have Scroll Remote Publishing Endpoint ready for Cloud as we are actually stuck with a requirement this issue would easily resolve. In general, publishing content with no or very low need for protection to a cloud instance of Confluence could be a quick and easy solution for many teams e.g. in terms of user guides, how-tos and stuff like that.
Unresolved
Details
Details
Assignee
Unassigned
UnassignedReporter

Components
Backbone Issue Sync
Backbone Issue Sync
Created November 17, 2016 at 2:15 PM
Updated June 19, 2023 at 10:11 AM
Update from
2023-06-19
Scroll Remote Publishing Endpoint has historically been a solution for users that needed to clearly separate internal and external environments. The external instance would have Scroll Remote Publishing Endpoint installed and host the content in the form of a Scroll Viewport help center, allowing public content without giving anonymous users access to the main (internal) instance.
Scroll Viewport for Confluence Cloud works differently from its Server counterpart and always creates a Viewport site that is always external to Confluence. Thus, the separation of environments is now an integral part of Scroll Viewport.
For this reason we have decided not to bring the Remote Publishing Endpoint to Confluence Cloud.