Apps / Approve for Confluence
Approve for Confluence records an approval against a page version, not the page. When an approved page is edited, the badge says so and links back to the version that was signed off.
Edit an approved page and the badge changes to “Edited after approval”, with the approved and current version numbers and a link to the approved one.
Choose the approvers and how many must approve: everyone, any one of them, or a number in between. After an edit, the next request starts with the same people filled in. Requests are posted as a page comment that mentions them.
Every page with an approval in one list: approved version, current version, approvers and rounds. Export it to CSV. People only see pages they are allowed to view.
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.
Approve for Confluence
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.
write:page:confluence, so it technically cannot).read:page:confluence read:blogpost:confluence read:space:confluence read:content.metadata:confluence read:comment:confluence write:comment:confluence read:user:confluence search:confluence read:content-details:confluence storage:appSend us an email about bugs, feature requests or anything else. We usually reply within 2 business days, in English or Japanese.