An approved page that changed is not an approved page.
Most approval apps record a decision and stop there. Someone edits the page a week later and the badge still says Approved. Approve & Lock binds every approval to the page version it was given for — so when the page changes, everyone can see that it did.
Security Policy
All production access requires multi-factor authentication. Reviewed annually by the security owner.
Approval history
- Editing locked to approvers
- Approved by Dani Silva at v12
- Approval requested
What it does
Binds to a version
Approved at v12 means approved at v12. A later revision makes the approval stale automatically.
Locks on approval
Optionally restricts editing to the approvers, then releases it when the page goes stale. Restrictions you already had are captured and restored, never overwritten.
Fails honestly
If a lock cannot be applied the app records it and falls back to flagging. It will not tell you a page is locked when it isn't.
Append-only audit
Every event with its revision — requested, approved, locked, unlocked, stale — on the page and embeddable as a macro.
Re-review dates
Approvals can expire on a date. Overdue pages surface on the space dashboard.
Runs on Atlassian
No external servers, no third parties, no analytics. No page content is stored — only that a page changed, and at which version.
Deliberately not
Electronic signatures, multi-step conditional workflows, or a validated quality-management system. If you need those, buy those.