How to see who has read a Confluence page
The request usually arrives the same way. A new code of conduct, a security policy, a changed procedure goes up in Confluence, and someone from HR, security or quality asks: can we get everyone to confirm they have read it, and can we prove who has not? A company-wide announcement does not answer that, and neither does a view counter.
This article goes through what Confluence Cloud gives you for this, in the order worth trying, and says what each option does not do. It ends with one paragraph about the app we make for it. If you delete that paragraph, the rest should still help you; that is the test we wrote it to.
1. First decide which question you are answering
"Who has read this page?" hides three different questions, and the right tool depends on which one you have:
- Who opened it? A view, measured by Confluence. Useful for reach, useless as evidence: opening a page is not reading it.
- Who signed off on it? An approval by a few named people before or after publishing. The content is being judged.
- Who confirmed they read it? An acknowledgement by everyone in a group, often dozens or hundreds of people, recorded per person and per version. The content is not being judged; the reader is saying "I have read this".
Policy attestation, handbook sign-off and "read and understood" for procedures are the third question. Most of the frustration in community threads on this topic comes from trying to answer it with a tool built for the first or the second.
2. Analytics: who opened the page
On Standard, Premium and Enterprise plans, the byline shows how many people have viewed a page, and selecting it opens an analytics summary with views and unique viewers over time (Content insights and analytics). On Premium and Enterprise, the summary also lists viewers, marks each as Engaged (viewed for 20 seconds or longer) or Brief, and shows the latest version they viewed and when (View Confluence analytics). Admins control which groups may see analytics (Control which groups can use analytics).
What it does not do. It records presence, not intent. Twenty seconds on a twelve-page policy is not reading it, and a person who read it carefully on a colleague's screen does not appear at all. On Premium and Enterprise a Mentions tab can filter the people @mentioned on the page by viewed or not viewed, which comes closest to "who has not looked yet"; for anyone not mentioned, and for a group, you compare the list against your directory yourself. Either way it is still a view. As a source for "did people get to the page?" it is good. As evidence that a person accepted a policy, an auditor or an HR lead will rarely take it.
3. Approvals: a few people sign off
Confluence Cloud now has native approvals, announced as an open beta (Approvals in Confluence, now on Open Beta). A space admin turns on statuses with approvals for the space; a requester asks named reviewers to approve a page; each reviewer responds with Approve or Request changes, optionally with a comment; and an activity log keeps past approval cycles, who approved or asked for changes, and when (Request and manage approvals in Confluence). Atlassian's announcement puts the open beta on Premium and Enterprise, for pages; a Community walk-through reports up to 10 approvers per request (Confluence Approvals (Beta): the four gates); check Atlassian's page for your plan, since beta terms change.
What it does not do. It is built for judging content, not for confirming reading. The people in it are a handful of named reviewers, not a group of 200 employees, and "Request changes" is the wrong second button for someone who has simply read the code of conduct. If your procedure needs the policy owner and a manager to approve before publication, use it for exactly that, and pair it with one of the options below for the readers.
4. Task lists: the do-it-yourself read confirmation
The workaround you will find most often in community answers is a task list at the bottom of the page: one checkbox per person, each assigned with an @mention. Assigned tasks show up in each person's task list, and a task report macro on another page can list the ones still open (Insert the task report macro).
For a team of eight and a policy that changes once a year, this is a perfectly good answer. Try it before buying anything.
What it does not do. Three things, and they grow with the group. The list is typed by hand, so when someone joins the team, nobody is asked. A tick is not tied to a version: when the policy changes, the old ticks still stand unless someone clears them all by hand, and then the evidence of who read the old version is gone. And a checkbox is page content, so whoever can tick their own box can usually tick someone else's; the page history shows who did it, but an auditor has to dig for it.
5. What an acknowledgement record needs
Put those limits side by side and the shape of a real read confirmation falls out. For each page that must be read, it needs:
- An audience that follows your directory: a Confluence group, so new joiners are asked without anyone editing the page.
- A record per person: who confirmed, when, and which version of the page they confirmed.
- A rule for new versions: either a new version asks everyone again, or a minor edit keeps earlier confirmations valid. Both are legitimate; the choice should be written down.
- The missing names: a list of who in the group has not confirmed, not only who has.
- A nudge for the people on that list, that does not depend on someone remembering to send it.
- An export that can be handed to an auditor or HR without screenshots.
If you only need the first two for a small team, a task list and a disciplined owner cover them. Past that, it is a tool's job.
What we make
Northwick Apps makes Acknowledge, a Confluence Cloud app built to that list. On any page, you pick the Confluence group that must read it, choose whether a new version re-requests acknowledgement or accepts confirmations from a version you name onward, and add an optional due date. Readers get an I have read this button under the title that records the page version they confirmed and when. The acknowledgement report lists every person in the group with their status, version and time, and exports as CSV; a dashboard lists every tracked page; and, with reminders switched on, a weekly comment on the page @mentions whoever has not confirmed. It works with groups of up to 5,000 members, stores account IDs, versions and timestamps rather than page content or names, and runs entirely on Atlassian's infrastructure. It is being prepared for the Atlassian Marketplace; this paragraph will carry the listing link the day it is public. Until then, our Security page says what we do and do not have.