Ties an approval to a specific version of a page, not to the page itself. If the page is edited after approval, the badge takes back "approved" on its own.
Works with: Confluence Cloud
What we tell you up front
This app records only the approvals requested after it was installed. Approval history from before that does not exist anywhere, so it cannot be imported.
The badge changes to "Edited after approval (approved v9 / now v12)", with a link to the approved version and a link to the change log. The approvers are notified by a comment. This behavior is the reason this app exists.
It posts one comment on the page and @mentions the approvers. Confluence itself sends the notification email, so it carries the page title and a link, and each person's own notification settings are respected. This app never sends email anywhere outside. It uses no external service and no API key.
No. The dialog opens with the previous approvers already filled in. Editing the page does not clear the approver list.
"History" on the badge shows, version by version, who approved or rejected, when, and what they said. You can also export it as CSV from the approval ledger (one row per decision).
There are three: everyone approves / one person approves / n people approve. A single rejection settles the round (a rejection is treated as a stop condition, not as one vote in a majority).
It does not. Blocking edits is a job for Confluence page permissions, and it goes wrong when an app takes that over. This app solves it from the other side: it does not hide the fact that the page changed.
It cannot. A regulated electronic signature, such as one under 21 CFR Part 11, is a different thing. This app is a record of approval, not a signature.
They were never recorded, so they do not appear. Recording starts with the approvals requested after installation.
It does. The badge appears on blog posts as well, and if one is edited after approval the display changes the same way and the approvers are notified.
It does not. Only records for pages you can view. Page titles, approver names, and rejection comments from spaces you have no permission for appear neither on screen nor in the CSV. The number of excluded records is shown on screen, so when you use this for an audit, open it with an account that has view permission on every space in scope.
When an approval is requested, when someone responds, and when an approved page is edited, it posts one comment on that page. It does not rewrite the page content (it does not request write:page:confluence, so it technically cannot).
Approval records are never deleted automatically. This app exists to keep them as an audit record, and a record that disappears at a deadline would defeat the point. Rounds are capped at 25 per page, and anything beyond that drops off oldest-first (storage is also capped at 60KB per page). Uninstalling the app deletes the Forge storage along with it (if you reinstall within Atlassian's retention period, the earlier records may still be there).
read:page:confluenceread:blogpost:confluenceread:space:confluenceread:content.metadata:confluenceread:comment:confluencewrite:comment:confluenceread:user:confluencesearch:confluenceread:content-details:confluencestorage:appSee the Privacy Policy for details.
Contact us via Support. We aim to reply within 2 business days.