We have various people within our organization who want to force a review of Confluence pages and require approval prior to the pages being published. Specifically, they wish to control Confluence pages in such a way that the content is essentially View-Only. I know how to lock down permissions at the space level and at the page level to control content, but what I'm being asked for sounds like a job for GITHUB... something which would require a PR to merge requested changes to a document, which would then be published as view-only content within Confluence.
Despite my reluctance to pursue this approach, I understand the need for control of some content in this manner. Is there a recommended solution for such a use case?
Randy
