How to use Page Approval

Last updated: 28 August 2026

Page Approval answers one question honestly: was this page approved, and is what I am reading right now the thing that was approved? Everything below exists to keep that answer true. This page covers every screen, what each label means, and — at the end — what the app deliberately does not do.

The one idea worth reading first. An approval belongs to a version of a page, never to the page. So when someone edits an approved page, the app does not keep saying "Approved". It says "Approved on version 7 — the page is now on version 9, with 2 changes since then", and it gives you the link to see what changed. That is the whole product.

1. Getting started — there is nothing to set up

Install the app and it works. Anyone who can edit a page can send it for approval and choose who should sign it off, right there on the page. Space defaults exist (section 4) but they are optional: they only save people from repeating themselves.

2. The badge on the page — what everyone sees

Every page gains a small Approval item on the byline, next to the author. It shows one short label, without anyone clicking anything:

LabelWhat it means
Not submittedNobody has asked for approval on this page.
Waiting for approval · 1 of 3A request is open and one of three approvers has signed off.
ApprovedApproved, and the page is still on the version that was approved.
Approved · page changedApproved once, but the text has moved on since. This is the state no other app in this category shows.
Changes requestedSomebody returned it with a written reason.

Clicking the badge opens a small panel with three things and nothing else:

3. The decision window

Opened from the badge with Review. One window, four blocks, no tabs.

What is being decided

The page title and the version the request was opened on. If the page moved after it was sent, an amber banner says so and offers See what changed. Nobody approves in the dark.

Who has to sign

One line per person or group, with the face and the name:

A group counts as one line. Anyone who can edit the page can add or remove an approver here, and signatures already given are never wiped — a person added later simply starts as "waiting". App and bot accounts are refused as approvers: Atlassian's picker offers them, but a page waiting on a robot would wait forever, so the app says which account it refused and why.

The decision

Two buttons. Approve records your signature against the version you are looking at. Request changes opens a text box and the reason is required — the button stays off without one, and the server refuses it too.

The Approve button disappears when there is nothing left for you to sign, so the same version cannot be signed twice. This matters: a log that counts clicks instead of decisions is not evidence.

The written reason is stored and colleagues read it. Treat it like a page comment: say what needs changing, and do not put personal or sensitive information in it.

The history

Collapsed at the bottom: one line per decision, newest first — v7 · approved · Ana Silva · 26 Aug 2026, 14:12 — and each line opens that version. The history never disappears, not when a signature goes stale and not when a subscription lapses.

4. Space defaults — optional

In a space, open Space settings → Page approval. The screen opens by saying so itself: approvals already work in this space, and these settings only set the defaults. Four questions:

  1. Who approves by default? People or groups. Leave it empty and whoever sends a page chooses at that moment.
  2. Is one signature enough, or must everybody sign? Everybody, by default.
  3. Which pages are covered? Only pages someone sends for approval (the default); every page carrying a chosen label; or every page under a chosen parent page.
  4. Who can change this? Only someone who administers the space. This is checked on the server, so it is a real restriction, not a hidden button.

A half-finished setting — choosing "every page with a label" and leaving the label empty, for example — is refused with a message that says what to do.

5. The space report — the screen a company buys the app for

In a space, open Page approvals. One row per page, with the state recalculated against today's version, who still has to sign, the last decision, and the links to open the page, open the approved version, see what changed, or take a decision.

Five numbers sit at the top: how many pages the report covers, how many are approved, how many are approved but changed since, how many are waiting, and how many were returned with changes requested.

The filter nobody else has: only pages that changed after approval. That is the list of pages that currently claim to be approved and are not telling the truth. If you are preparing for an audit, start there.

Other filters: state, approver and label. Export CSV gives you the same rows as a spreadsheet, with names written out rather than account codes.

When the report cannot read everything, it says so. The app reads the space page by page to the end. If some pages could not be read, a line at the top states plainly that the totals are short and invites you to try again — it never quietly shows a smaller number as if it were the whole picture.

6. Approvals — the inbox in the top menu

Apps → Approvals in the Confluence top navigation. Three tabs, each with its count in the title:

Review opens the page, on purpose. Signing happens on the document itself, in the badge. This app will not let anyone rubber-stamp a queue of approvals without opening what they are approving.

7. The approval stamp in the exported PDF

Insert the optional Approval stamp macro at the top of a controlled document. It draws a box showing which version was approved, by whom and when — and that box comes out in the PDF when the page is exported, with the date the PDF was produced.

If the page has moved on since it was approved, the printed box says so in bold: "This page is now on version 2, with 1 change since it was approved. What you are reading has NOT been approved." A printed copy of a controlled document that cannot tell you it is out of date is worse than no copy at all.

The macro is optional. The badge on the byline works on every page without it.

Two things to know about Confluence's PDF export, neither of them ours: it can sit at "0% complete" for a few minutes before finishing all at once, and the file arrives through a progress page with a download link rather than downloading straight away.

8. What invalidates an approval, and what does not

What happenedDoes the approval still stand?
Someone published a new version of the pageIt is flagged — the state becomes "Approved · page changed", with the count of changes and the link to see them.
A label was added or removedYes. Confluence does not change the page version for a label, and neither do we.
The page was renamed or movedYes.
An approver was added or removedYes — existing signatures are kept. A new approver simply starts as "waiting".
The space defaults were changedYes. Nothing already signed is reset.

This table exists because the most common complaint about apps in this category is the opposite behaviour: an approval quietly wiped by a change that had nothing to do with the text.

9. What the app does not do

10. Support

Email support@saoirsesoftware.com, or open a request on our support portal. English, business days, and we aim to reply within two business days. Emails reach the person who writes the code.

← Back to Page Approval