eDiscovery and Preservation for Confluence

Confluence is a content collaboration platform that helps teams work together and share knowledge. It’s often utilized as a wiki or intranet by over 40,000
organizations worldwide.

By integrating directly with Confluence’s API, Onna collects all data and metadata from an entire Confluence site or individual spaces in their native format for both Confluence on the web and on-premise, making Onna the most comprehensive eDiscovery collection tool for Confluence.

Using Onna with Confluence

Collect, process, preserve and search across your Confluence site and spaces in real-time. 

Most development teams use Confluence as an internal wiki or intranet, so it’s often a relevant source of discoverable data, especially when the case involves IP. However, at this time, Confluence doesn’t offer a workflow for eDiscovery or legal hold.

By integrating with Confluence’s API, Onna ensures you collect and preserve all available data and metadata, including comments, attachments, and historical information, in a defensible and scalable way. Audit logs of all collections and processing activity are included for defensibility.

All collected data, including images, audio and video files, is processed, indexed, and OCR’d instantaneously, rendering a fully searchable environment of your entire Confluence site and/or individual spaces. Relevant data can be exported and uploaded to your existing eDiscovery workflows and review platforms for a seamless experience.

Some of our Customers

Join these cutting-edge companies using Onna to enhance their eDiscovery and knowledge management strategies

Main Features

API Based Collections

By connecting with Confluence’s API, Onna collects all available data and metadata, including file attachments, labels, and historical information.

Data Preservation and Legal Hold

Preserve and hold Confluence for your entire site or individual spaces on Onna. In addition to Confluence, Onna offers preservation across all its integrations.

eDiscovery Exports

Export relevant Confluence data in a custom load file and upload it onto a review platform for further assessment. Exports include the natives and metadata.

How to Collect from Confluence with Onna

Check out our app on the Atlassian Marketplace

Confluence on the Web Integration Features

Onna supports Confluence Cloud and Server version 5.7 and up.

What is collected?

Onna connects directly with the API to collect all information in native format. The integration collects all data and metadata from an entire Confluence site or individual spaces.

All files are synced, including, but not limited to:

  • HTML content of the page
  • Comments on pages
  • Attachments for the page
  • Labels for attachments and pages
  • Ancestors for the page/attachments
  • Historical information and related metadata, including:
  • Author of the page
  • Created by/on
  • Last updated by/on
  • Previous Version created by/on

What are your sync modes?

We currently support three syncing modes – one-time, archive, and auto.

  • One-time sync collects data during a certain time range or up until the date the source was added. This is great for one-time eDiscovery collections.
  • Archive means that Onna will perform a full sync first and will continuously add any new files generated at the data source. The sync type does not delete files deleted or edited from Confluence, ensuring you always maintain a preserved and archived copy of your Confluence data.
  • Auto-sync means that Onna will perform a full sync first and will keep the data source and Onna in mirrored sync. Any deletions from the data source will be deleted in Onna, as well.*

The synchronization scope currently encompasses entire Confluence sites and specific Confluence spaces and/or pages.

*This sync mode is only supported for Confluence pages and files attached to a space.

Check out our app on the Atlassian Marketplace

Confluence On-Premise  Integration Features

To collect from Confluence on-premise you will need Onna’s desktop app and an Onna Enterprise account.

What is collected?

All files are synced, including, but not limited to:

  • HTML content of the page
  • Comments on pages
  • Attachments for the page
  • Labels for attachments and pages
  • Ancestors for the page/attachments
  • Historical information and related metadata, including:
  • Author of the page
  • Created by/on
  • Last updated by/on
  • Previous Version created by/on

Onna’s sync modes

For on-premise collections, we currently support one-time syncs.

  • One-time sync collects data during a certain time range or up until the date the source was added. This is great for one-time eDiscovery collections.

The synchronization scope currently encompasses entire Confluence sites, specific Confluence spaces, and specific Confluence pages.

Frequently Asked Questions

How is Onna deployed?

Onna can be deployed as a SaaS product or in your private cloud. We also integrate with SAML & SSO services, like Okta, GSuite or Active Directory.

How is Confluence data rendered in Onna?

Confluence pages are rendered in HTML format. Other files, such as attachments, are rendered in their native format.

Does Onna collect attachments on Confluence pages?

Yes, attachments and files posted on pages are collected and maintain the parent-child relationship.

How does Onna work?

Onna connects directly with each source’s API to extract all available metadata and data. After the connection is made, data begins syncing and undergoes a layer of processing and OCRing, rendering a searchable and indexed repository of your data. You can begin searching immediately within Onna or export the relevant files onto a review platform.

Can I export individual pages from a Confluence site?

Yes, you can select individual pages, specific spaces, or your entire Confluence site. You an also export only data relevant to your search results.

How much does Onna cost?

We offer both usage-based or per user pricing to scale up or down as needed.

Ready to begin? Contact us to get started.