Paperlatch
Guide · Checked against Atlassian's documentation on 14 October 2026
If an auditor asks who changed a policy page, who moved it to another space, or who deleted it, the Confluence audit log is the first place most admins look. For those three questions it is usually the wrong place.
Atlassian's audit log documentation lists these categories of events: spaces, users and groups, global administration, permissions, public links, content, and templates — and notes that the list is not exhaustive. In practice it is a record of how the site is configured and who has access to what.
The same page says so directly:
“The audit log doesn’t record information related to content edits (you can view this in the version history)” — and it excludes changes to a content’s location.
That leaves three gaps that matter in an audit:
There are three honest options. You can rely on version history and accept that moves and purged pages are invisible. You can build an Automation rule that comments on a page when it moves — workable for one space, hard to keep complete across a site. Or you can install an app that listens to Confluence's content events and keeps its own record.
Two limits you should know before relying on any tool of this kind: