Approval Seal Approval Seal for Confluence — user guide
What it does
An approval in most tools records that someone once clicked Approve. Approval Seal binds the approval to the page version it was granted against. When the page is edited, the seal breaks and the badge says so.
Installing
Install from the Atlassian Marketplace. It is free for sites of 10 users or fewer. No configuration is required and no setup screen has to be visited — the badge appears on pages immediately.
Everyday use
Open any page. Under the title, next to the author, you will see Approval status. Click it.
| Badge | Meaning | What you can do |
|---|---|---|
| Not controlled | No approval record for this page | Request approval |
| Awaiting approval | Someone has asked for approval of this version | Approve · Request changes |
| Approved | Approved, showing who and which version | — |
| Stale | Approved earlier, but the page has been edited since | Re-request approval |
| Changes requested | A reviewer asked for changes | Re-request approval |
Requesting approval
Open the panel and choose Request approval. The request is recorded against the page's current version, with your name and the time.
Approving
Open the panel and choose Approve. The approval is bound to the version shown. Request changes stops the workflow instead and records why it stopped.
When a page is edited
Nothing to do. Publishing an edit invalidates the approval within seconds. The badge turns red and reads "Stale — approved at v12, page is now v13". The original approval is not deleted — the history keeps it, so you can still see what was approved and when.
History
The panel lists recent events for the page: requests, decisions, and invalidations, each with the version and the person involved. This is what to show an auditor who asks "who approved this?".
Current limitations
Stated plainly so nobody is surprised:
- One approver. Multi-approver quorum is not configurable yet.
- No space-level policy. Pages are put under control individually, on demand.
- No org-wide dashboard. Status is per page.
- Live Docs are not covered. Use classic pages for content that needs approval.
- Approvals are not enforced. The app makes staleness visible; it does not prevent anyone from editing an approved page. This is deliberate — a space admin can override any restriction, so a lock would be a promise the platform cannot keep.
A note on compliance
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. Ask your quality lead how it fits your validated process.
Support
Contact the support address on the Marketplace listing. Please include your site URL and the page ID if a specific page is involved.