Compliance Release Notes 2023

Compliance for Confluence Cloud receives regular updates to add new features, improve the app, and fix bugs or emerging vulnerabilities.

If you have any questions or need assistance please contact our Customer Support team.

🛠️ Improvements	Minor text changes to improve the explanation of specific features in Compliance for Confluence
🐛 Bug fixes	Various bug fixes and security improvements

💎 New Features	Added custom sensitive data detectors Admins can configure custom detectors using regular expressions For more information, check our documentation
🐛 Bug fixes	Various bug fixes and security improvements

🐛 Bug fixes

Fixed an issue where users would get stuck in the set level modal when in the page editor for an extended period of time

💎 New Features	Default classification can now be applied at the space level Individual spaces can be given unique default classification levels For more information, check our documentation
🐛 Bug fixes	Users without restrictions permissions can now set classification levels on pages when the level and the page have no associated restrictions Various bug fixes and security improvements

💎 New Features

Added default classification which allow admins to configure a level to be applied automatically to pages when published
- This is currently only applicable at the global level
- For more information, check our documentation

🛠️ Improvements	Updated the time stamps within Compliance to show the actual date rather than a relative date (e.g. 1 month ago) Updated the descriptions on various user interface screens for greater clarity Added the “Space Type” field to the Scope settings
🐛 Bug fixes	Fixed a bug that prevented blog posts from being published when Enforce Classification was enabled

💎 New Features	Added sensitive data detection capabilities. Admins can now use a set of built-in detection rules to identify sensitive data within the Confluence instance For more information, check out our documentation
🐛 Bug fixes	Fixed a problem that prevented Confluence groups with “&” in the name from being added to the Page Restrictions configurations in Compliance

🐛 Bug fixes