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 Portal to register an OAuth 2.0 application (or the ability to generate an API token from your Atlassian Account Settings).
  • Read access to all Confluence Cloud Spaces and Pages that the connector should manage.
  • Knowledge of your Confluence Cloud domain (e.g. yourcompany.atlassian.net).
• You know which Confluence Cloud Spaces should be included in or excluded from ingestion.

Step 1 – Add the Confluence Cloud Connector in RecordPoint

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

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

Step 2 – Configure (but do not enable) the Connector

On the Confluence Cloud Connector Details page, complete the required configuration fields:

Note: When entering your Confluence domain, do not include the https:// prefix or the .atlassian.net/wiki suffix. Enter only the subdomain, for example yourcompany.

Save the connector configuration.

Important: Ensure the connector Status remains Disabled. Do not enable ingestion yet. You will enable the connector only after you have authorised the application in Atlassian Confluence Cloud (see Steps 3–4 below).

Step 3 – 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 Portal to obtain credentials.

1. Navigate to the Atlassian Developer Portal at https://developer.atlassian.com/apps/.
2. Click Create and select OAuth 2.0 integration.

3. Enter the following settings:

   Setting	Value
   Name	RecordPoint Confluence Cloud Connector
   Description	Used by RecordPoint to read Confluence content for records management.
   Callback URL	Provided by your RecordPoint implementation contact

4. Under Permissions, add the following OAuth scopes:

   Scope	Purpose
   read:confluence-content.all	Read pages, attachments, and page metadata
   read:confluence-attachment.all	Download attachment binaries
   read:confluence-spaces.summary	Enumerate Spaces
   read:confluence-user:me	Identify the authenticated user
   read:comment:confluence	Read footer and inline comments

5. Click Save.
6. Note the Client ID and Client Secret generated for the application.

Security note: Grant only the scopes listed above. RecordPoint requires read-only access to Confluence content. Do not grant write or admin scopes.

Step 4 – Authorise the RecordPoint Connector Application

Once your OAuth 2.0 application is registered, authorise the connector to access your Confluence Cloud instance.

1. Return to the RecordPoint Platform and open the Confluence Cloud Connector you created in Step 1.
2. Enter the Client ID and Client Secret from the application you registered in Step 3.
3. Click Authorise to initiate the OAuth 2.0 flow.
4. You will be redirected to Atlassian to sign in and grant the connector access.
5. Sign in with a Confluence Cloud user account that has read access to all Spaces the connector should manage.
6. Review the requested permissions and click Accept.

Alternative — Basic Auth (development and testing only): If OAuth 2.0 is not yet available, you may use a Confluence Cloud API token. Generate a token at https://id.atlassian.com/manage/api-tokens and enter your Atlassian account email address and the API token in the connector's Basic Auth fields. Basic Auth is not recommended for production deployments.

Inform your RecordPoint contact (or internal project owner) when authorisation is complete so they can proceed with enabling and validating the connector.

Step 5 – Enable the Confluence Cloud Connector in RecordPoint

Once the OAuth application is authorised:

1. Return to the RecordPoint Platform.
2. Open Settings → Connectors and select the Confluence Cloud Connector you created earlier.
3. Review the configuration settings and update any remaining fields as required.
4. 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.
• The initial full synchronisation processes approximately 100,000 pages within a 24-hour SLA window.

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.