Simple page approval for Confluence Free and Standard plans. Request a review, see each approver's decision, and know exactly which version was approved, with a badge that changes the moment the page is edited again. It runs entirely on Atlassian.
Why "native"?
Approval records live on the page. Each page's approval history is stored as a Confluence content property. It moves with the page when it is moved, copied or migrated, and is deleted with it.
Runs on Atlassian. The app is built on Atlassian Forge and is eligible for the Runs on Atlassian programme. It sends no email and makes no calls outside Atlassian; approvers are notified through Confluence's own @mentions.
Paid from day one, free up to 10 users. No free app that later turns paid.
Features
A badge next to every page title. Draft, In review, Approved v12, Changes requested, or Edited since approval. Click it for the current request, each approver's decision and comment, and the full history.
Request approval from the page menu. Choose approvers, the rule (any one approver, or all of them), an optional due date and a note.
Approved-version tracking. The approval is tied to the page version it was given on. Edit the page afterwards and the badge becomes "Edited since approval", with one-click re-approval. A space can start re-approval automatically.
Change a request while it's open. Add, remove or replace approvers without starting over.
Approvers who leave never block a review. Deactivated or closed accounts are shown as "Unavailable" and don't count towards "all approvers".
My approvals. A dashboard under Apps: waiting for me, my requests, recently approved, and pages edited since approval.
Defaults per space. Default approvers, the rule, automatic re-approval and notification comments, on one settings page. Site-wide defaults for Confluence admins.
Nothing hidden when a licence lapses. An inactive licence pauses new requests and decisions. Every status and history stays readable.
Getting started
Install Native Page Approvals for Confluence from the Atlassian Marketplace.
On any page, open the … menu and choose Request approval. Pick approvers and a rule.
Approvers get a Confluence notification. They open the page, click the badge next to the title, and Approve or Request changes.
A space admin can set default approvers under Space settings → Integrations → Page approvals.
See everything waiting for you under Apps → My approvals.
How it works
The rules
Any one approver: the first approval approves the page.
All approvers: every available approver must approve.
Request changes needs a comment and closes the review under either rule, so a blocking objection is never outvoted silently. The requester edits the page and requests re-approval, which starts a new round.
Approving a version you haven't seen is refused. If the page changed while the panel was open, the approver is asked to reload.
Self-approval is off by default. The requester is left out of the approver list.
Notifications
When approval is requested, the app posts a footer comment on the page that @mentions each approver, so Confluence sends its normal mention notification. Decisions post a comment that mentions the requester. These comments are visible on the page, which is how Confluence notifies people; they can be switched off per space or site-wide.
Who can do what
The app uses each person's own Confluence permissions.
Anyone who can edit a page can request approval for it.
Listed approvers can decide. They need to be able to view the page, not edit it.
The requester or a space admin can change approvers or cancel.
Space admins change space settings; Confluence admins change site settings.
Limits
Edits aren't blocked. Confluence apps can't reliably stop someone editing a page. Instead, every edit after an approval is made visible: the badge changes, the dashboard lists the page, and re-approval is one click. If you need a hard lock, use Confluence's own page restrictions after approval.
Pages only. Blog posts, whiteboards and databases aren't supported.
No email reminders or escalation for due dates. Overdue requests are flagged in the panel and on the dashboard.
The badge updates when the page loads, not live.
Approvers need access to the page to act; the requester can replace an approver who can't see it.
FAQ
Why not Confluence's built-in approvals?
Confluence's native approvals are available on Premium and Enterprise plans. Native Page Approvals is for teams on Free and Standard, and for teams who want the approved version tracked and visible.
Where is our data stored?
Approval records are stored on your pages, as Confluence data. Settings and the dashboard index are in Atlassian's Forge storage for your site. The app stores account IDs of requesters and approvers, and no names, emails or page titles. See the privacy policy.
What happens if our licence lapses?
New requests and decisions are paused. Badges, panels and history stay readable on every page. Nothing is hidden or deleted.