How to Implement Document Review & Audit Process in Confluence

[Sudarsana Goddellagala]

I’m looking for suggestions on implementing a mandatory document review and approval process in Confluence.

Currently, we are able to manage reviews using comments and status macros, but there doesn’t seem to be a way to enforce approvals before a document is considered final or audit-ready.

Has anyone implemented a solution (with or without add-ons) to ensure:

Mandatory review before approval
Clear audit trail of who approved and when
Prevention of changes after approval
Would appreciate any best practices or approaches that have worked in your organizations.

Thanks in advance!

[Maja Vallin · Accepted solution]

Hi there,

I would use the page status function in Confluence to set the status and combine that with Confluence automations to achieve this. This is just what I thought of the top of my head.

For example: When a page is published: change status, restrict page and notify approval

This would perhaps need more adjustments like only pages that is published with correct template or something like that

And then for the approver: When the user changes the status of the page: update the restrictions for everyone to see

This one would also need some adjustment to who is triggering the event and what kind of page perhaps

I Would also perhaps use Confluence databases to gather all these pages to get a good overview of all pages, statuses, owners of pages etc. 

You could also use automations to notify or change statuses for pages that needs to be reviewed again after x amout of time.

Hope this gave you some inspiration to where to begin