How to add read confirmation to Confluence pages

Guide · Checked against Atlassian's documentation on 20 October 2026

Confluence Cloud has no built-in read confirmation — no native button that lets every reader say "I have read this", with a report of who has and hasn't. Two built-in features come close, on Premium and Enterprise only:

Page analytics shows who viewed a page — which is a different thing (more on that).
Approvals let you ask named people for a formal sign-off on a page, with Approve or Request changes, comments and an activity log (Atlassian: request and manage approvals). If you need a handful of named people to sign off a policy and you are on Premium, try this first — it costs nothing extra. Its limits for read confirmation: everyone who responds needs edit permission on the page, and a space can require at most five approvers, so it does not fit "all 200 employees must confirm they have read the security policy".

So for read confirmation across a wider audience, you have three options.

Option 1: a table on the page (free, manual)

Add a two-column table at the bottom of the page — Name and Date — and ask readers to add a row.

✅ Works today, on any plan.
❌ Anyone with edit rights can change anyone else's row.
❌ Readers need edit permission on the page, which you may not want to give.
❌ Nothing tells you who is missing, and the table does not know when the page changes.

Fine for a team of five. Not something to show an auditor.

Option 2: an external form (free or cheap, manual matching)

Link a Microsoft Forms or Google Forms acknowledgement from the page.

✅ Reliable names and timestamps.
❌ The form does not know which version of the page someone read.
❌ You build the "who hasn't confirmed" list by hand, by comparing the responses with a group.

Option 3: a Marketplace app (paid above small teams)

A read confirmation app adds a button to the page and keeps the record for you. Several exist. By installs on Confluence Cloud (Atlassian Marketplace, 20 October 2026), the most established are QC Read and Understood and Comala Read Confirmations, with a handful of newer ones.

A checklist for choosing one

These are the questions that separate the apps, and you can answer most of them from each Marketplace listing without installing anything:

Can you set an audience? You want a group that must confirm, so the app can list who hasn't — not just a list of who did.
Is the record tied to a page version? When the page changes, earlier confirmations should be kept, and a new round should start.
Is there one report across spaces? If you have policies in several spaces, a per-page view means opening every page before an audit.
What permissions does it ask for? Open the Privacy & Security and Permissions tabs on the listing. Look for write access to your content, acting on a user's behalf, and access to email addresses — and ask whether a read confirmation tool needs them.
Where does the data live? Look for the Runs on Atlassian badge, which Atlassian gives to Forge apps that meet its conditions for keeping data on Atlassian's platform (details). An app without the badge is not necessarily storing data elsewhere — Forge apps can use Atlassian's storage or the vendor's — so read each listing's Privacy & Security tab for where its data is kept.
What does it cost at your size? Most are free for up to 10 users. Above that, prices differ a lot — compare at your actual user count on each listing's pricing tab.

Where Confirm & Chase fits

We make Confirm & Chase, so take this as the vendor's description, checked against the list above:

Yes — you pick the group that must confirm, and the Not confirmed tab lists who hasn't.
Yes — a new version starts a new round; earlier rounds stay in the record and the CSV.
Yes — one dashboard across every space.
Read-only access to pages, users, groups and content permissions. No write access to your content, no acting on a user's behalf, and email addresses are never read or stored.
Runs on Atlassian Forge.
Free for up to 10 users.

Setting it up (Confirm & Chase)

Install it from the Marketplace listing.
Edit the policy page and insert the Confirm & Chase macro.
In the macro settings, pick the group that must confirm. Save, and publish the page.
Readers see an I have read and understood button.
Open the global Policy compliance page (from the Apps menu) to see who has confirmed and who is outstanding, and export the CSV when you need it.

Paperlatch makes Confirm & Chase.