Baselines for Confluence is a Confluence Cloud app for creating and managing baselines of Confluence space content. A baseline captures selected versions of pages, blog posts, and attachments within a space by referencing the content as it existed at a specific point in time. Teams use Baselines for Confluence to establish content milestones, compare baselines, and review changes across their Confluence content, providing a structured way to track the evolution of documentation and other space content.
Installing Baselines for Confluence
Baselines for Confluence can be installed on your Confluence Cloud site either from the Atlassian Marketplace or through the Confluence administration pages.
To install the app from the Atlassian Marketplace, search for Baselines for Confluence by OBSS, open the app listing, ensure the Cloud version is selected, and click Try it free. Then select the Confluence site where you want to install the app and click Start Trial.
Alternatively, navigate to Confluence Administration → Atlassian Marketplace → Find New Apps, search for Baselines for Confluence by OBSS, click Try it free, and then select Start Free Trial in the Add to Confluence dialog.
In both cases, Atlassian automatically installs the app on your Confluence site together with a trial license.
Learn more: Installing Baselines for Confluence Cloud
Creating a Baseline
Baselines are created from the "Baselines for Confluence" page in the Apps section of the Confluence space menu, and require the Create Baselines permission. When creating a baseline, you give it a name and choose one of two creation types:
With "Based on a Date", you enter a date and the app includes the oldest version of each item in the space that is dated before the given date. The scope can be the whole space with the "Include All Items" option or a set of individually selected items, and attachments on the included items are added automatically. With "By Selecting Individual Item Versions", you select items one by one and choose a specific version for each from a version picker, which is set to "Latest" by default. No date is entered with this option, and the scope is automatically set to individual item selection.
After clicking Create, the baseline is generated in the background. Its progress is displayed in the baseline list, where the creation process can also be cancelled. Once complete, the baseline becomes accessible from the list.
Learn More: Creating a Baseline
Viewing a Baseline
Selecting a baseline from the list on the "Baselines for Confluence" page displays its contents. Each row shows an item's title, type, location, the version included in the baseline, and the date of that version. For pages and blog posts, a compare-with-latest option is also available. Item titles link directly to the corresponding baselined version.
Learn More: Viewing a Baseline
Comparing Baselines
Any two baselines can be selected from the list and compared. The results are grouped into three lists: items included only in the first baseline, items included only in the second baseline, and items included in both baselines but with different versions. Items with different versions provide links to both versions and a compare option. Items with the same version in both baselines are shown only as a total count. The compare page can be searched by item name or path and filtered by item type.
Learn More: Comparing Baselines
Deleting Baselines
A baseline can be deleted using the trash can icon next to its name in the baseline list, which requires the Delete Baselines permission. This action is permanent and cannot be undone. However, since a baseline contains only links to item versions rather than the items themselves, deleting a baseline does not delete any pages, blog posts, or attachments; your content remains in the space.
Learn More: Deleting a Baseline
Configure Permissions
The Baselines for Confluence Permissions page allows Confluence admins to define which user groups can view, create, and delete baselines. It is accessed via Confluence Administration → Apps → Baselines for Confluence Permissions.
Learn More: Configure Permissions
Rate Limiting
Baselines for Confluence applies rate limiting to prevent overuse of the service. Rate limits cap how many reports can be requested within a set time period across all request types, including the main reporting screen, dashboard gadgets, issue view screen tabs, the REST API, and file exports. The exact limits are not published and are set well above typical usage, so normal daily use should not reach them; they mainly apply to REST integration scenarios sending many requests in a very short time. When a limit is hit, requests return an HTTP 429 response.
Learn More: Rate Limit
Server/DC to Cloud Migration
The Server/DC to Cloud migration path for Baselines for Confluence is currently under development, and you can contact the support team for up-to-date information about migration. All sales and licensing operations are handled directly by Atlassian, so questions about app licensing when migrating to Cloud should be directed to Atlassian. Note that if data is imported into a Cloud instance and Baselines is installed more than once, errors can occasionally occur, because a second import overwrites all instance data and the app then tries to register as a clean install; the support team can resolve this by manually removing the registration. For any questions or support requests, you can reach the team at https://appsupport.obss.tech/ or appsupport@obss.tech.
Learn More: Server/DC to Cloud Migration
Server/DC and Cloud Feature Comparison
A feature comparison table documents which Baselines capabilities are available on Server/DC versus Cloud. Some features are supported on both platforms, while others are currently available on only one of them. The table is updated as new features are introduced.
Learn More: Server/DC and Cloud Feature Comparison
Server/DC to Cloud Migration with CCMA
Baselines data can be migrated from Confluence Server/Data Center to Confluence Cloud using Atlassian CCMA, provided the Data Center instance runs Baselines for Confluence version 2.8.3 or later. The migration transfers baseline definitions and baseline permissions, recreating them in Cloud exactly as they exist on Server/DC. Any group that does not exist in Cloud is still migrated but logged as a warning. In repeated migrations, a baseline definition is overwritten only when one with the same name already exists in the same Cloud space, while baseline permissions are always fully overwritten by the latest Server/DC configuration.
Learn More: Server/DC to Cloud Migration with CCMA