Confluence’s audit logs do not provide itemized tracking for each page in a bulk move. They log high-level events like space creation or permission changes, but not the success/failure of individual page moves.

🔍 Use Cases

• Customers require detailed logs for all content changes — especially page moves — including:

• • Who moved the page

• • When it was moved

• • From which parent/page/location to which destination
    Currently, the logs don't capture sufficient metadata to meet our internal or regulatory audit requirements.

• When pages are accidentally moved or changed without proper documentation, the limited logging makes it difficult to trace the action or restore the previous structure accurately.

• For large documentation sets, the structure is critical. Without clear traceability, it becomes hard to maintain quality and consistency across content hierarchies.

• In shared spaces, knowing who moved what and where is important not only for accountability, but also to avoid:

• • Duplication

• • Broken links

• • Misplaced or hidden content

---

🚨 Impact

• When pages go missing or are relocated silently, end users often assume the content has been deleted or lost. This results in:

• • Repeated support requests

• • Wasted effort

• • Reduced confidence in Confluence

• Teams spend time searching or recreating pages, leading to delays and reduced productivity.

• For regulated teams, this logging gap can create audit risks and compliance concerns.

• Admins and space owners currently have no native way to track page moves, leading to:

• • Manual workarounds

• • Heavy reliance on Atlassian Support

• • Difficulty resolving incidents quickly