Summary

Space admins should be able to view space-level analytics (including personal/user-level data within their space) without being granted access to site-wide analytics. Currently, analytics permissions are all-or-nothing at the site level — there is no way to separate space analytics access from site analytics access.

Customer Use Case

The customer manages a large Confluence Cloud environment where each space admin is responsible for the health and adoption of their own space. Space admins regularly rely on space-level analytics to:

• Identify which content is actively used and which can be cleaned up or archived

• Spot important pages that need to be highlighted or updated

• Measure whether internal communications (announcements, guidelines) are reaching the intended audience

Current Behaviour

Analytics permissions are controlled at the site level under Settings > Security > Analytics Permissions. Once a group is granted analytics access, users in that group can see both site-wide and space-level analytics, including personal user data (e.g., unique views per user) at the site level.

This forces admins into an undesirable trade-off:

1. Enable analytics globally → Exposes site-wide personal analytics data to all users with analytics access, raising privacy and compliance concerns (e.g., visibility into how many unique views a specific user has across the site)

1. Disable analytics entirely → Removes all analytics access, including useful space-level insights that space admins need for their own spaces

The customer has chosen option 2 (disabling analytics for admin groups), which is a step back from their desired workflow.

Suggestion by customer: 

• Space admins should be able to view space-level analytics (including personal/user-level data) for spaces they administer, without requiring site-level analytics permissions

• Site-level analytics (cross-site user activity, global usage data) should remain restricted to site admins only

• Ideally, personal data in site analytics should be anonymised or hidden for non-site-admin users, while remaining visible within space analytics for space admins

Business Impact

• Privacy & Compliance: Current behaviour exposes personal usage data (unique views per user) at the site level to anyone with analytics access, which raises data privacy concerns

• Adoption & Content Health: Space admins lose visibility into content usage patterns when analytics are disabled, reducing their ability to maintain and improve their spaces

• Admin Overhead: Without granular permissions, site admins must choose between privacy risk and loss of functionality — there is no middle ground

Affected Customers

Organisations with large Confluence environments and distributed space ownership, where space admins need analytics to manage their own spaces but should not have visibility into site-wide personal data.