Read & Understood Acknowledgements for Confluence
Per-version read confirmations with reports for audits and compliance.
Get it on the Atlassian Marketplace →
Overview
Ask people and groups to confirm that they have read and understood a Confluence page, such as a policy or a procedure, and keep a record of who confirmed which version and when.
- Required readers: people, groups or both.
- Confirm again after each new version, or once is enough.
- Confirm from the page header or from a signature box inside the page.
- Page report, space report and a personal list of pending reads.
Set up a page
- A Confluence administrator installs the app from its Atlassian Marketplace listing.
- Open the page and, in the page header under the title, select Read & understood, then the Settings tab. Only people who can edit the page can change it.
- Turn on Require read confirmation on this page.
- Add Required readers (people) and/or Required readers (groups).
- Under When the page changes, choose Ask everyone to confirm again after each new version or One confirmation is enough.
- Select Save.
Optional: edit the page, type / and insert the Read & understood signature box macro, so readers can confirm inside the page.
Confirming a page
Readers open Read & understood in the page header, tab My confirmation, or use the signature box, and select I have read and understood this page (version N).
If the page requires a new confirmation after each version and it has changed since you confirmed, you are asked to read it again.
Reports
| Report | Where | What it shows |
|---|---|---|
| Page report | Page header → Read & understood → Report | Who confirmed which version and when, who is pending and whose confirmation is outdated. |
| Space report | Space settings → Integrations → Read & understood report | Every page of the space that requires confirmation, with its version, rule, required readers and how many of them are up to date. |
| My pending reads | Sidebar → Apps → My pending reads | The pages waiting for your confirmation, with the current version and the version you confirmed. |
Moving from QC Read and Understood for Confluence
Atlassian ends support for Connect, the platform used by QC Read and Understood for Confluence, on 31 January 2027. This app is built on Forge and runs on Atlassian's cloud.
- Before you uninstall the other app, export or save its reports: they are your record of past confirmations.
- Install this app and turn on read confirmation on the pages that need it, with their required readers.
- Where pages used the other app's signature box, insert the Read & understood signature box macro instead.
Confluence administrators can open Confluence administration → Settings → Apps → Read & understood. Enter a space key and select Scan space to find the confirmation records that a previous read-and-understood app left in Confluence. Importing those records into this app is planned for a future version.
Limitations
- Confirmations are recorded per page version. Confluence keeps the page history; the app records which version each person confirmed.
- Group members are resolved when the report is built, so people who join a required group later appear as pending.
Permissions
| Scope | Why |
|---|---|
storage:app | Store page settings and confirmations. |
read:page:confluence, read:space:confluence | Page title and version, and the pages of a space for the reports. |
read:confluence-content.permission | Only page editors can change the settings. |
read:confluence-groups, read:confluence-user | Required groups, their members and the groups of a user. |
Data and privacy
For each page: the settings (required account IDs and group IDs, and the rule). For each confirmation: the Atlassian account ID, the page version and the date. Page content is never stored. Everything is kept in Atlassian's Forge storage; no data leaves Atlassian. Once a week the app reports the stored account IDs to Atlassian, as Atlassian requires, and when an account is closed its confirmations are deleted and it is removed from the page settings. See the privacy policy.
Troubleshooting
I do not see the Settings tab
Only people who can edit the page can configure it.
Someone confirmed but still appears as outdated
The page changed after they confirmed and the rule asks for a new confirmation after each version.
The app says it needs an active license
The app is paid and checks the license on every request. Ask your site administrator to check the app's subscription in the administration of Jira or Confluence (Apps → Manage apps). During a free trial the app works normally.
Need help?
See the support page.