Page Acknowledgements for Confluence Cloud
Know who has read your important Confluence pages.
Ask people or groups to confirm they have read a page. PageAck records who acknowledged it, which version, and when. Export the record whenever someone asks for proof.
- Runs on Atlassian Forge
- Your records stay inside Atlassian
- Free for up to 10 users
Built for policies, procedures and anything people must read
For page owners in HR, security, quality and operations who need an answer to one question: has everyone read the current version?
A record tied to the page version
Each acknowledgement stores the version of the page that person confirmed. An acknowledgement of version 11 never counts for version 12.
Asked again when it matters
Ask again every time the page is edited, on a schedule such as every 12 months, or only when you decide to.
One click for readers
Readers see a banner at the top of the page and confirm with Read and Understood. There is nothing new for them to learn.
Evidence you can hand over
Export a CSV listing who has and has not acknowledged, with versions and UTC timestamps. Nobody can edit or delete a record in the app.
How it works
Three steps, all inside Confluence.
-
Choose the page, the people and the rules
Start from the page menu or from the app. Pick Confluence groups or individual people. Group membership is refreshed every day, so new joiners are asked without you doing anything.
Then decide when to ask again and how long people have.
-
Readers confirm on the page itself
Everyone in the audience sees a banner on the page with its due date. They read, tick one box and confirm. The app records their account, the page version and the time.
-
See who is done, then export the record
Each page shows who has completed, who is outstanding and who is overdue. One button exports the current status as a CSV file. A second export gives every acknowledgement ever recorded for the page.
User Status Acknowledged At (UTC) Page Version Due (UTC) Sarah Chen Completed 2026-09-15T08:00:00.000Z 12 Emma Wilson Completed 2026-09-14T09:00:00.000Z 12 Hugo Blanc Outstanding 2026-10-13T15:00:00.000Z Priya Patel Overdue 2026-09-27T15:00:00.000Z Five of the columns in the status export, with sample data. The file also carries email, account ID, page ID and export time.
Where teams use it
Any page where someone might later say they never saw it.
| Team | Typical pages | What the record gives you |
|---|---|---|
| People and HR | Code of conduct, remote work policy, employee handbook | Every employee confirmed the current version, including people who joined after it was published. |
| Security and IT | Information security policy, acceptable use policy | A dated sign-off per person, repeated every year. Auditors often ask for this list. |
| Quality and operations | Standard operating procedures, work instructions | A fresh acknowledgement after every revision, tied to the revision number. |
| Engineering | Incident response, on-call runbooks, coding standards | The team has seen the latest procedure before they need it. |
Security and data
PageAck runs on Atlassian Forge. It has no servers of its own, and the app declares no access to any outside network.
What is stored
- Atlassian account IDs of the people asked, and page IDs
- Page titles, version numbers and timestamps
- The groups you select, and any message you add for readers
- A history of changes to each requirement
What is not stored
- Names and email addresses. Exports read them from Confluence at the moment of export.
- Page content
- Anything outside Atlassian. Records live in the app storage Atlassian hosts for your site.
Who can see what
- People who can edit a page can require acknowledgement on it and see its records. Admins can limit this to Confluence administrators.
- Readers only see their own status.
- Confluence permissions are checked on every request, using the signed-in person's own access.
What we do not claim
- PageAck holds no third-party security certification.
- It records acknowledgements. It does not make an organisation compliant with any standard on its own.
The 7 permissions the app requests
read:page:confluence and read:confluence-content.summary to read a page's title and version. write:page:confluence to switch the banner on for a page. It does not edit page content.
read:confluence-groups to list groups and their members. read:confluence-user and read:user:confluence to show names in the app and in exports. search:confluence to find a page by title during setup.
Pricing
Billed by Atlassian with your other Marketplace apps. One edition with every feature.
Up to 10 users
Free
For small Confluence sites.
11 users and more
$0.40 per user, per month
For example, about $40 a month for 100 users. Larger sites pay less per user.
Paid sites start with a 30-day free trial through Atlassian. If a subscription lapses, new requests and acknowledgements pause, and everything already recorded can still be viewed and exported.
Questions
Does it send email reminders?
No. People see a banner on the page, and a list of everything assigned to them under Apps, Page Acknowledgements. Email reminders are not built.
What happens when the page is edited?
You choose. By default every published edit asks everyone to acknowledge the new version. You can turn that off for a page, in which case earlier acknowledgements keep counting and each record still shows the version that was acknowledged.
Can I require acknowledgement for a whole space at once?
No. Requirements are set page by page.
How many people can one page have?
Up to 5,000 people per page, added through groups or individually.
Can a record be changed or removed?
Not in the app. Acknowledgements and the history of each requirement are only ever added to. Closing a requirement stops new requests and keeps every record.
What happens to the data if we uninstall?
Atlassian deletes the app's stored data after its retention period. Export anything you need to keep before uninstalling.
Does it work on Confluence Data Center?
No. PageAck is for Confluence Cloud only.
Will this make us compliant with ISO 27001 or SOC 2?
No tool can do that by itself. PageAck gives you the list of who acknowledged which policy version and when, which is one piece of evidence such audits commonly request.
Start with one policy page.
Setup is three steps and happens entirely inside Confluence.