keelapps/Signoff
For teams whose pages need a real sign-off
Who approved this version of this page — and is that still good?
Confluence cannot answer that question. Signoff can, because its approvals pin the exact page version they covered: edit the page and the badge degrades to “Approved · page changed” on its own, computed live against the page and never stored. Policies are defined once and bound to spaces by reference — govern three hundred spaces without copying a workflow into any of them.
Free for sites up to 10 users. Above that it is priced per user per month and billed by Atlassian — see pricing on the Marketplace.
Quality manuals, SOPs, release notes, legal copy — pages whose whole value is that someone stood behind a specific version of them. The native page has no approval concept at all, and the apps that add one are heavyweight workflow engines configured space by space by hand, with records held on servers outside Atlassian.
What it does
Sign-off in one click
Request approval from the page itself: approvers come from the space's policy or your own pick, any-one or all-must-approve, with an optional note to the approvers.
A badge that cannot lie
An approval names the page version it covered. The badge compares that against the live page every time it renders — “Approved · v12” becomes “page changed” the moment anyone edits, with re-approval one click away.
One policy, every space
Define approvers, mode and validity once. Spaces bind by reference or simply inherit the site default; editing the policy updates every bound space at once. Nothing is ever copied.
Approvals that expire
A policy can give approvals a validity of 3 to 24 months. A daily scan surfaces everything due for re-approval — site-wide for admins, and in each signer's own inbox.
Notified by Confluence itself
Approvers are @-mentioned in a page comment, so requests reach them through Confluence's own bell and email — and the approval trail is visible on the page. Admins can switch the comments off.
An audit trail an auditor can use
Every request, decision and cancellation, exportable as CSV: who approved which version of which page, and when. Built on Forge, zero external calls.
An SOP review, end to end
-
The policy exists already
The site admin defined “Quality documents” once: two named approvers, everyone must approve, valid for twelve months. The QMS space inherits it without any setup.
-
The author requests sign-off
One click on the page. The approvers are @-mentioned in a comment and the request lands in their approvals inbox; the badge reads “In review”.
-
Approvers decide from the queue
Approve or request changes right from the inbox, with a comment. The moment the request settles, the badge reads “Approved · v7, valid until next August”.
-
The truth maintains itself
Someone edits the page in March — the badge degrades to “page changed” by itself. Next August the approval expires and the page appears on the due list. Nobody had to remember anything.
Against what you have today
| Question | Native Confluence | Workflow suites | Signoff |
|---|---|---|---|
| Who approved this exact version? | No approval concept | Sometimes, buried in a workflow | On the page |
| Page edited after approval — does the status notice? | — | Often stays “approved” | Degrades by itself |
| Same rules across 300 spaces? | — | Copy the workflow 300 times | One policy, bound by reference |
| Approvals that expire on a compliance calendar? | — | In the heavyweight tiers | 3–24 months, built in |
| Audit export for the auditor? | Page history only | Varies | CSV, one click |
| Do approval records leave Atlassian? | — | Usually — vendor servers | Never |
Availability
Signoff is live on the Atlassian Marketplace. It is built and deployed on Atlassian Forge and installs into your Confluence Cloud site straight from the listing.
Licensing is handled by Atlassian. Sites with 10 users or fewer pay nothing at all; paid tiers are priced per user, at a fraction of the heavyweight suites.
Questions, bug reports and feature requests: raise a support request.
Found a security issue? Please report it privately rather than in a public channel.