Overview

Secure Content for Confluence provides a means to encrypt, protect, view, and track activity on all your sensitive information in any page within Confluence. Secure content is stored in blocks that can be referenced in multiple locations with a unique secure content key. Once a key is created, it can be used to access the block from any page simply by adding the macro and referencing the key.

This page explains the following:

• Macro parameters: Lists the parameters to be defined through the macro editor
• Secure content block components: Explains the various components of a secure content block such as ownership, permissions, and content changes
• Request access: Explains how to ask for access to view and/or update the required secure content block

Macro parameters

Edit a Secure Block Content macro from the page to see the macro editor.

The following parameters are available in the macro editor:

Secure content block components

Open the Secure Content by Bob Swift Atlassian Apps window to see the various components of a secure content block. To see this window:

• Edit the block from the page, if you have the required permissions, or,
• Edit the page, select required Secure Content Block macro, and click Content.

Here, there are three tabs; click any tab name to view further details:

• Editor
• Permissions
• Owner

Editor

Users and groups with Admin or Edit permissions can modify existing content, view previous versions of the content and restore to previous versions (select required version and save). Similar to Confluence versions, the selected version is treated as the current version, and new revisions take the next revision number in the sequence.

In the Editor, you can:

• Provide styles such as bold, italics, underline to your text;
• Create bulleted or numbered lists;
• Add or remove links;
• Add headings from large to small, or, enter normal text;
• Undo or redo the changes made to the text; and,

• Save your changes, Cancel your changes, or Delete this block.
  

  When a block is deleted, a Restore button appears in the editor that allows you to undo the delete and get the latest contents back. You can then make any required changes and save the block contents as usual.

Permissions

There are four permission sets available for your secure content, with descending levels of access as follows: Owner, Admin, Edit, and Read.

Permission set specific features

	Read content	Edit content	Add permissions	Grant access	Control notifications	Transfer ownership	Delete & restore	Implicit authentication
Read
Edit
Admin
Owner

Owner

The first user to add content to a Secure Content Block macro is established as its owner and has full rights to secure content and its owner-level features:

• Notification Level
  Receive Confluence notifications of activity on your secure content. Select between: Read, Edit, Admin, and None notification levels. Notifications levels are successively constrained where:
  • Read: Notifications are sent to the owner for every activity on the secure content.
  • Edit: Notifications are sent for every update made to the secure content.
  • Admin: Notifications are sent if any permission sets are changed.
  • None: No notifications are sent to the owner regardless of the activity type.
• Transferable
  By default, Confluence administrators in the Secure Content Administration view can 'take ownership' of your secure content. Deselect this option to make this feature unavailable, and thus, no transfer of ownership can occur regardless of Confluence privilege.
• Implicit Render
  For convenience, you may want your content to render without authorized users having to put in their Confluence password each time. Select this option so that authorized users can view the content directly once the page with the secure content is refreshed.
• Labels
  Create labels for your secure content to filter your Secure Content Owner Reports. (Label filters available since Secure Content 2.1)
• Secure Content Audit
  Keep track of access or changes to your secure content with an exhaustive audit of its activity over time. 
• Delete and Restore
  No longer want your secure content to be available? Use the Delete button and your secure content gets removed from view regardless of user's permission. When a block is deleted, a Restore button appears in the editor that allows you to undo the delete and get the latest contents back.
  

Admin

Owners and administrators (users with Admin permission) can add and remove Confluence users and groups and assign permission levels here.

Request access

Read-only users do not have access to the Content editor window. But users can access content through the page view by entering their Confluence password, or, if secure content has Implicit Render enabled, the content renders on page view automatically.

If you do not have access to a secure content block, a Request Access () button is displayed next to the block. The Request Access button opens up a dialog box where you can send a customized message (optional), requesting for better access of that secure content block, to its owner. The owner receives a notification of your request and if the access is granted, you get a notification back. You can keep requesting for a higher level of access until you get the required level of access.

Process to request access

For example, if you have Read access to a secure content block, you can request for an Edit access or Admin access from the owner. To do so, you have to specify in the custom message what kind of access level you require. If you do not write a custom message, usually, an immediate higher level of access is granted.

1. Request higher access on secure content block:
   
2. Write customized message (optional) and send the message:
   
3. Owner grants the required access. Now, you can edit this secure content block:
   

Which of the access levels can be requested/granted?

• Read
• Edit
• Admin