Compliance Release Notes 2025

💎 New Features

• Added in-app feedback surveys

  • Written feedback can now be given from directly within the app by clicking the “Feedback” button in the top right of any page

💎 New Features

• Added automatic AI Classification classification

  • Admins can now enable automatic AI classification for selected spaces or site-wide.

  • While enabled, Compliance will use an LLM to analyze your page content for sensitivity, confidentiality and risk, before applying the classification level it deems to be best suited.

  • For more information, check our documentation

🛠️ Improvements

• Classification method added to the classification history modal

  • Distinguish between manual or automated classifications when viewing the classification history of a page

• Classification history timeline view added to the classification history modal

  • In this view, more information on sub-level and method is available.

• Replaced various icons in the navigation bar

• Added confirmation when bulk editing space settings

• Enabled searching by space name when a space is chosen using the bulk classification feature

• Dark mode support added to the dashboard and search pages

🐛 Bug fixes

• Fixed a bug where detections too long in length would fail to process

💎 New Features

• Added detector schemes

  • It is now possible to use different detectors within different Confluence spaces, providing more flexibility than was previously available.

  • For more information, check our documentation

🛠️ Improvements

• Added custom detector type icons

  • When creating custom data detectors, users can now select from a number of icons

💎 New Features

• Added classification settings bulk edit

  • The space-level classification settings can now be managed in bulk, allowing much faster configuration of multiple spaces

• Added classification settings space defaults

  • Admins can now configure a set of default classification settings to be applied to newly created spaces

🛠️ Improvements

• Made the Compliance Cloud REST API reference is now accessible from within the app administration area

• Added support for Confluence’s dark mode to remaining elements of the Compliance Cloud app UI.

  • Compliance Cloud is now fully dark mode compatible 🎉

• Added selection of roles (such as Space Admin and Page Owner) to the email automation rule.

• Classification can now be enabled and disabled in all personal spaces using a single toggle when managing globally.

• Updated the on-page detections modal to list the detection types that are being scanned for on that page.

Removal

• The deprecated /instance endpoints in the Compliance REST API have been removed.

  • Page classification should instead be managed using the /page-level endpoints

💎 New Features

• Added a REST API for Compliance Cloud functionality

  • Added a series of REST API endpoints to enable programmatic access to classification levels, data detections, and other Compliance-related functionality.

  • Confluence admins can create and manage API keys with limitations on classification level, space, and action scope

  • For more information, check our documentation

  • See the full API reference

🛠️ Improvements

• Added dark mode support to some additional UI components.

💎 New Features

• Added a new and improved search page available to all users.

  • The updated search page allows both classification levels and sensitive data (where enabled) to be searched in one unified interface.

  • Users can also take direct action from the search page, such as applying classification levels to pages

• Added support for live docs

  • Both classification and sensitive data detection is now available on live docs as well as pages.

  • Note that sensitive data detection scans are conducted when a page is snapshotted by Confluence, which takes place at the end of an editing session.

🛠️ Improvements

• Users can now classify pending pages directly within the Pending Classification table of the Compliance dashboard.

🐛 Bug fixes

• Fixed a bug where Automation Rules were ignoring Excluded Pages and Exclusion Rules. Now, Automation Rules will not be triggered by pages that have been excluded, or by detections that should be ignored due to an active Exclusion Rule.

• Fixed a bug where the “Exclude Page” action in the detection results modal would fail on new, draft pages.

💎 New Features

• Added new tabs to the admin dashboard

  • Sensitive data - provides insights into data detections across your Confluence instance, allowing administrators to quickly identify what kinds of sensitive data have been detected within Confluence and pinpoint where these have been introduced.

  • Space detail - provides a consolidated view of page classification and data detection insights, and relates each of these together, for a chosen Confluence space.

💎 New Features

• Added a new admin dashboard to the Compliance administration area

  • This dashboard gives admins summarised statistics of classification across their entire Confluence instance

• Users can now redact sensitive data directly from the on-page sensitive data detections modal.

• Admins can now exclude pages from sensitive data detection directly from the on-page sensitive data detections modal.

🛠️ Improvements

• New Compliance Banner UI – Moves the classification level lozenge and sensitive data results button into a unified Compliance banner at the top of your Confluence pages

  • Displays the classification level directly on space home pages

  • Shows the count of sensitive data detections on each Confluence page

  • Allows classification levels to be set directly within the page editor

  • Clearly communicates configuration statuses (e.g., when features are disabled and why), sub-levels, and app access

  • Introduces a new button linking directly to the Compliance app, providing easy access to key tools such as the Classification search

• Admins can now override hierarchy-based classification, allowing them to lower the classification level of pages even with this setting enabled.

  • Updated the non-admin UI to note that admins can override the hierarchy-based classification.

🐛 Bug fixes

• Fixed a bug where data detection scans would fail on pages created or last updated by anonymous Confluence users.

Removal

• Removed the ‘Set Classification Level’ action within the Confluence page menu. Users can set a classification level using the level lozenge present at the top of the Confluence page.

• Removes the ‘Add to Excluded Page’ action within the Confluence page menu. Admin users can exclude a page from data detection via the detection results modal, accessed by clicking the detections lozenge at the top of the Confluence page.

🛠️ Improvements

• Added a new getting started page to the automation rules section

  • This page provides guides and resources for using the automation rules functionality

• Began the process of migrating to the Atlassian Forge platform.

• Added user analytics to the app

  • Admins can enable or disable app analytics at any time from their app settings

• Updated the Compliance macro to include page sub-level on export

🐛 Bug fixes

• Fixed an issue where the on-page classification indicator and macro were not correctly rendering in dark mode.

• Resolved overlapping UI elements when editing schemes (in Admin settings).

• Fixed an issue where view-and-search and view-only sensitive data detection permission settings were not correctly enforced.

💎 New Features

• Added new automation rule action types

  • Label - apply a page label when triggered

  • Email - send an email notification to selected users or groups when triggered

  • Redact - remove the detected content and replace it with a black redaction bar when triggered

    • Optionally will delete the historic page version where the text was detected

    • This action cannot be reversed

• Updated audit logs to include entries for automation rules

  • For redaction automation rules, the detected text will appear in the audit log.