Paperlatch
Can you see who viewed a Confluence page? (And why it isn't proof they read it)
Guide · Checked against Atlassian's documentation on 20 October 2026
Short answer: on Confluence Cloud Premium and Enterprise, yes — page analytics lists individual viewers. On Standard, you see how many people viewed a page, not who. And on any plan, a Confluence admin can turn on privacy mode, which replaces viewer names with hashed usernames.
That answers the question as asked. But if you are asking because you need to know whether people read something — a policy, an SOP, a security procedure — a page view is the wrong evidence. More on that below.
What each plan shows
| Plan | What you see about viewers |
|---|---|
| Free | No content insights |
| Standard | Total views and estimated read time in the byline; a chart of views and unique viewers |
| Premium, Enterprise | The full page analytics screen, including a per-viewer list: engagement, last version viewed, last viewed, number of views |
Source: Atlassian, Content insights and analytics. If the view count does not appear in a page's byline, your plan does not include content insights.
How to check who viewed a page (Premium and Enterprise)
- Open the page.
- Select the view count in the byline, under the page title.
- Select View all page analytics.
- The overview lists viewers, with the last version each person viewed.
Privacy mode can hide viewer names
Confluence admins can turn on Hide personal data in analytics (Settings → Security → Security configuration). Atlassian's documentation says this "will replace user names and avatars with a hashed user name", and that repeat views by the same person are no longer recorded. Views recorded while privacy mode is on stay anonymized, even if it is turned off later.
Source: Atlassian, Turn on privacy mode for analytics data.
So whether you can see names depends on your plan and on a setting that someone else controls.
Why a page view is not evidence that someone read a policy
If an auditor asks you to show that employees have read the information security policy, page analytics will not answer the question. Four reasons:
- A view is not a statement. Opening a page for two seconds counts as a view. Nobody said "I have read and understood this".
- There is no audience. Analytics tells you who came. It does not tell you who should have come and didn't — and that is the list you actually act on.
- It is not tied to what they agreed to. If the policy changed last month, you need to know who confirmed the current version, not who opened some version at some point.
- It depends on a setting. With privacy mode on, there are no names at all.
When ISO 27001 or SOC 2 audits ask about policies, a common way to show that people were told about them is an attestation — typically a named person, the version of the document they saw, a timestamp, and a record that survives the next edit. Whether your auditor asks for this, and in what form, depends on your own controls and their request list; neither framework prescribes a specific form.
What to use instead
If you only need a rough sense of reach, page analytics is fine and costs nothing extra on Premium.
If you need a record you can hand to an auditor, you need a confirmation step on the page itself. Confluence does not have one built in, so this means a Marketplace app. Several exist — QC Read and Understood and Comala Read Confirmations are the most installed.
We make one of them: Confirm & Chase. It adds a confirmation button to a page, and you pick the group that must confirm. One dashboard shows who confirmed and who is outstanding, across every space. When the policy changes, a new round starts and earlier rounds stay on record. It runs on Atlassian Forge with read-only permissions, and it is free for up to 10 users.
Paperlatch makes Confirm & Chase. Checked against Atlassian's documentation on 20 October 2026.