Overview

Secure Content 2.1 includes some new features that were the most requested by end users like allowing administrators to re-assign ownership of content to anyone, improved owner notifications with custom messaging and a more robust reporting macro as well as a few minor bug fixes of course.

New features

Administrators Assign Ownership to Any User

Previously the administrator could take ownership of a Secure Content block provided it was "transferable". Now they can assign ownership to anyone in Confluence.

Contact Secure Contact Owner With Custom Messages

Previously those desiring access to a Secure Content block could click the "Request Access" button that would notify the owner. Now they can customize a message that will be delivered to the owner's Confluence inbox.

Secure Content Reporting Macro Improvements

Secure Content Reporting macro was introduced in Secure Content 2.0. It lets you create lists of Secure Content blocks you or others own. We've improved it to let you wildcard by key name and list by user permission.

Issue and Bug Fixes