Confluence Cloud — Configuration

Use this guide to add, authorize, and enable the Confluence Cloud connector so that RecordPoint can manage content effectively.

Prerequisites

Before you begin, ensure:

You have the Application Administrator role in the RecordPoint platform (to add and configure connectors).
You have appropriate permissions in Atlassian Confluence Cloud:
- Access to the Atlassian Developer Console to register an OAuth 2.0 application.
- Read access to all Confluence Cloud Spaces and Pages that the connector should manage.
You know which Confluence Cloud Spaces should be included in or excluded from ingestion.

Step 1 – Create an OAuth 2.0 Application in the Atlassian Developer Portal

RecordPoint connects to Confluence Cloud using OAuth 2.0 (Authorization Code Grant with PKCE). You must register an application in the Atlassian Developer Console before configuring the connector.

Navigate to the Atlassian Developer Console at https://developer.atlassian.com/console/myapps/.
Click Create and select OAuth 2.0 integration.
Enter an app name such as RecordPoint Integration and click Create.

Under Permissions, select Confluence API and add the following scopes:

Granular scopes:

Scope	Purpose
`read:attachment:confluence`	Read attachment metadata and binaries
`read:comment:confluence`	Read footer and inline comments
`read:content:confluence`	Read page content
`read:content-details:confluence`	Read extended page metadata
`read:label:confluence`	Read page labels and classification tags
`read:page:confluence`	Read page data
`read:space:confluence`	Enumerate Spaces
`read:user:confluence`	Read user information for audit trails
`delete:attachment:confluence`	Delete attachments during disposal
`delete:comment:confluence`	Delete comments during disposal
`delete:content:confluence`	Delete content during disposal
`delete:page:confluence`	Delete pages during disposal
`delete:space:confluence`	Delete spaces during disposal

Classic scopes:

Scope	Purpose
`read:confluence-content.all`	Read all Confluence content
`read:confluence-content.summary`	Read content summaries
`manage:confluence-configuration`	Access configuration required for connector operation

Click Save.
Add the Callback URL, e.g. https://aue.records365.com.au/administration/connectors/genericcallback
Go to Settings for the app and note the Client ID and Client Secret — you will need these in Step 3.

Step 2 – Add the Confluence Cloud Connector in RecordPoint

Log into the RecordPoint Platform as an Application Administrator.
Click the Settings icon in the top main toolbar.
Click Add Connector.
In the Connector Gallery, select the Confluence Cloud Connector.
Click Add.

The Confluence Cloud Connector Details page displays. The connector instance has been created, but is not yet enabled.

Step 3 – Configure the RecordPoint Connector Application

Once the connector is configured, authorise it to access your Confluence Cloud instance.

Open the Confluence Cloud Connector in RecordPoint.
Complete the required configuration fields:
1. Enter as a comma delimited field.

Field	Description
Client ID	The Client ID from the OAuth 2.0 application registered in Step 1.
Client Secret	The Client Secret from the OAuth 2.0 application registered in Step 1.

Click Authorise to initiate the OAuth 2.0 flow.
You will be redirected to Atlassian to sign in and grant the connector access.
Sign in with a Confluence Cloud user account that has read access to all Spaces the connector should manage.
Review the requested permissions and click Accept.

Step 3 – Configure the Connector

On the Confluence Cloud Connector Details page,

Field	Description
Binary Ingestion Optional.	If Binary Protection is enabled then this setting can be used to disable the binary ingestion for this connector.
Space Filter (Include)	Add spaces that you want to include in ingestion.
Space Filter (Exclude)	Add spaces that you want to exclude in ingestion.

Change the connector Status to Enabled and click Save.

After the connector is enabled:

The connector will start operating according to the configuration you have set.
Confluence Spaces will be created as Aggregations in RecordPoint and Pages will be submitted as Records, along with their content, comment, and attachment Binaries.

Optional – Validation and Next Steps

After enabling the connector, you may want to:

Confirm that Spaces are appearing as Aggregations and Pages as Records in RecordPoint.
Check that classification rules and retention policies are correctly applied to the ingested Spaces.
Verify that Pages with attachments have the expected number of Binary items in RecordPoint.
Coordinate with your Records Management function to confirm that Page content, comment binaries, and attachment binaries are all present and correctly associated.
Review Space filter settings if certain Spaces should be excluded from ingestion.