Confluence Cloud — Overview

  • Updated

Introduction

The Confluence Cloud Connector enables RecordPoint customers to integrate their Atlassian Confluence Cloud environment with the RecordPoint platform for compliant records management. This connector captures Spaces and Pages — along with their associated content, comments, and attachments — to support retention, disposal, and records lifecycle obligations. It is particularly suited for organisations that use Confluence Cloud as a central knowledge repository and need to ensure business-critical content is not over-retained beyond its required retention period.

 

Key Capabilities

The connector uses a Space-Centric Aggregation approach: each Confluence Space is ingested as an Aggregation, providing the organisational boundary for retention policy assignment. Each Page within a Space is captured as an individual Record. Three types of binary content are ingested per Page: the HTML page body (for content analysis and PII detection), a rendered HTML document combining all footer and inline comments, and each file attachment uploaded to the Page. This model enables space-level holds, bulk disposal operations, and consistent retention governance across 100,000+ pages.

 

Default Managed Objects

Space (Aggregation)
└── Page (Record)
    ├── Page Content — HTML body (Binary)
    ├── Page Comments — footer + inline rendered as HTML (Binary)
    └── Page Attachment — uploaded file (Binary)

Detailed Entity Table

Source EntityRecordPoint Item TypeParentNotes
SpaceAggregationPrimary organisational container; retention policies are assigned at the Space level
PageRecordSpaceIndividual business document; the core entity for lifecycle management and disposal
Page ContentBinaryPageHTML/storage-format body of the page; ingested for content analysis and PII detection
Page CommentsBinaryPageAll footer and inline comments rendered as a single structured HTML document; includes author, date, thread hierarchy, and resolution status for inline comments; generated only when the page has at least one comment
Page AttachmentBinaryPageFile attachment uploaded to the page; one Binary per attachment file

Optional entities: Page Labels (custom classification tags) and Page Version metadata are captured as record metadata fields rather than discrete entity types. They are available for reporting and filtering but do not create additional Records or Binaries.

 

Additional Entity Types

Please contact RecordPoint support to discuss support for additional entity types.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request