How It Works¶
Content Retention Manager for Confluence handles information governance for Atlassian Confluence in the cloud. Keep what you need and remove what you do not.
- Retain content for a set or indefinite time.
- Purge content when it is no longer needed. Once purged, content cannot be recovered by admins or users, satisfying "non-discoverable" requirements for legal and compliance purposes.
Your Data within Content Retention Manager¶
Content Retention Manager for Confluence runs directly on the Atlassian Forge platform in your Confluence Cloud instance and does not transmit or retain any of your data, content, or user information on any external systems. The app is wholly contained within your Atlassian Cloud instance. When content is purged by Content Retention Manager, it cannot be recovered by users or admins. For more details, see the app's Privacy & Security page on the Atlassian Marketplace.
Recommended First Steps¶
Before getting started, we recommend you read through our content on Data Retention Policies and Management Best Practices and familiarize yourself with any Data Retention Laws and Regulations your team may need to comply with.
Info
We recommend you review all policies, practices, and processes related to this app with your company's legal representative before you begin enforcing any retention policies. This will help you remain compliant with any applicable laws or regulations.
Complete the following steps before deploying Content Retention Manager for Confluence:
- Understand why it is important to develop and implement data retention policies for your team.
- Familiarize yourself with laws and regulations you may already be subject to.
- Consider best practices when implementing content retention policies.
- Have a defined company retention policy ahead of time.
- Have an instance of Atlassian Confluence, Free, Standard, or Premium editions all work with Content Retention Manager.
Warning
We recommend testing Content Retention Manager for Confluence on a test or development instance of your Atlassian Cloud Confluence to get familiar with its functionality and to ensure that any automation you enable perform as expected before deploying to your production instance.
Accessing Content Retention Manager for Confluence¶
There are two ways to open Content Retention Manager for Confluence. What you see when you open it depends on your role and which edition is installed.
Apps menu¶
In the Confluence left side navigation, select Apps, then select Content Retention Manager.
Confluence administration¶
- Click the
icon in the top-right menu bar to open Confluence administration.
- On the left navigation pane, scroll down to Settings, then expand Apps.
- Select Content Retention Manager.
Who can access it¶
| Edition | Method | Admin | Non-admin |
|---|---|---|---|
| Standard | Apps menu | ||
| Confluence administration | |||
| Lite | Apps menu | ||
| Confluence administration |
Key Functions of Content Retention Manager¶
Info
Content Retention Manager for Confluence is available in both Lite and Standard editions. Refer to Edition Comparison for details on their differences.
| Function | Use |
|---|---|
| Content Audit | View all content and its current retention status. Admins can delete, purge, or extend the retention period of individual or multiple items from this view. |
| Policies | A policy defines the retention period for content. |
| Default retention | A default retention policy applies to all content in the absence of retention rules and extensions. |
| Retention Rules | Retention rules associate policies with entities such as spaces, users, groups, and classification levels. When a rule applies, the associated policy supersedes the Default Retention. |
| Classification Levels | A categorization that defines the information security sensitivity of content. |
| Classification Rules | Classification Rules associate Classification Levels with spaces. When a classification rule applies, the matching level is applied to content within the space and overrides the Default Classification. |
| Extensions | Extensions let content persist beyond its normal retention period, either to a specific date or indefinitely. An extension applies to individual items and overrides all policy settings. |
| Audit Log | The audit log helps you keep track of who updated policies and when. The log also records when content status changes to deleted and purged by user or automation. The audit log is how you monitor and keep a record of your retention policy in action. |
| Automation | Automation enforces your retention policies on a schedule, deleting, archiving and purging content automatically. |