Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-82632

Enterprise customers need extended and centralized audit log capability to verify past licensed user status across multiple sites

XMLWordPrintable

    • 1
    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      Enterprise customers need a way to verify whether a user has ever been a licensed (paid) user across multiple sites, beyond the current audit log retention limits (180 days for organization logs, 12 months for product logs).

      Environment / Context

      • Product: Confluence Cloud Enterprise
      • Customer environment: Large enterprise with 150+ Confluence sites under a single organization
      • Current limitation: Audit logs in Admin Hub (organization level) retain 180 days, product-level audit logs retain up to 12 months.
      • Use case: Customers must confirm whether an account was ever a paid user to comply with Atlassian’s guest user policy (guests cannot be current or past paid users).

      Current behavior

      • Admins can only check up to 180 days of history in organization audit logs.
      • Product audit logs provide up to 12 months, but must be checked site by site, which is impractical at enterprise scale.
      • No official method exists to verify license history beyond these retention limits.

      Expected behavior

      • Provide a centralized and scalable way for Enterprise admins to check whether a user was ever a licensed (paid) user across all sites in the organization, ideally with longer retention (multi-year) or unlimited historical tracking.
      • Ability to search or report at the organization level, without manually reviewing hundreds of site-level logs.

      Business impact

      • Enterprise admins cannot realistically confirm past paid status across 100+ sites, making compliance with Atlassian’s guest user policy difficult.
      • This creates operational risk, as admins may inadvertently register a former paid user as a guest, leading to policy violations.
      • Customers are concerned about audit/compliance readiness and license governance.

      Workaround

      • Admins can export product audit logs (per site) up to 12 months and maintain them externally, but this is not practical with hundreds of sites.
      • Organization audit logs cover only 180 days and are insufficient for the required historical checks.

      Additional notes

      • Customer feedback: “With more than 150 sites, it is impossible to check 12 months of product audit logs manually.

              Unassigned Unassigned
              9f3b28a42856 Kyungmin Kim
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: