Currently, once a document is published in a Confluence space connected to a JSM portal, it is immediately available to customers. However, for organizations that require content oversight, we need the ability to implement a multi-step approval workflow that ensures only the most recent, approved version of a document is made public.

Our current workaround involves using third-party tools like Comala Workflows and Comala Publishing to handle document approval and transfer approved versions to the portal. We would like to see similar functionality natively in Confluence Cloud, allowing for:

• Configurable approval workflows in Confluence.
• Automatic publication of approved content to JSM portals.
• Granular control to prevent unapproved or outdated versions from being accessible.