Approval Seal Approvals that break the moment the page changes
Most approval apps for Confluence record that someone once clicked Approve. They do not notice when the page is edited afterwards — so a page can carry a green Approved badge while its content has moved on.
Approval Seal binds every approval to the exact page version it was granted against. Edit the page and the seal visibly breaks: the badge turns red and reads “Stale — approved at v12, page is now v13.” Nobody has to remember to re-check, and nobody can accidentally rely on an approval that no longer applies.
What it does
- An approval badge sits under the page title, where readers already look.
- Request approval, approve, or request changes without leaving the page.
- Records who approved, when, and against which version.
- Editing the page invalidates the approval automatically and immediately.
- A per-page history shows every request, decision and invalidation.
What it deliberately does not do yet
Being straight about this, because a compliance buyer will find out anyway: there is no multi-approver quorum configuration, no space-level policy, no org-wide dashboard, and Live Docs are not yet covered. The app does one thing thoroughly rather than six things partially.
Built on Atlassian Forge
The app runs entirely inside Atlassian's cloud. No external servers, no third-party services, no network egress. It requests no write access to your content and cannot create, edit or delete pages. See the privacy policy.
Not a compliance certification
Approval Seal provides features your own validated process can use. It does not certify your organisation against ISO 9001, ISO 13485, SOC 2, 21 CFR Part 11 or any other standard, and no such claim is made.