Skip to content
Last updated

Confluence integration

Confluence is a team workspace and wiki platform by Atlassian for creating, organizing, and collaborating on documentation and knowledge bases. The Confluence integration with Frontegg allows your application to access and manage Confluence spaces, pages, and user data on behalf of your users.


Prerequisites

  • An Atlassian account with access to the Atlassian Developer Console
  • Permission to create OAuth 2.0 apps in the Atlassian Developer Console

Connect Confluence

Step 1: Open the Atlassian Developer Console

Go to developer.atlassian.com/console/myapps and sign in with your Atlassian account.

Atlassian Developer Console showing the list of existing apps

Step 2: Create a new OAuth 2.0 app

Click Create and select OAuth 2.0 integration from the dropdown.

Create dropdown with OAuth 2.0 integration option highlighted

Step 3: Fill in the app details

In the form that appears, enter the app name:

  • Name: Frontegg Integration

Create a new OAuth 2.0 integration form with app name filled in

Step 4: Accept the developer terms and create the app

Check I agree to be bound by Atlassian's developer terms and click Create.

Create form with name entered and terms accepted

Step 5: View the app overview

After creation, you are taken to the app overview page. This shows your app's details and navigation tabs.

Frontegg Integration app overview page

Step 6: Copy your credentials

Navigate to Settings to find your Client ID and Secret.

App Settings page showing Client ID and Secret fields

Save your Secret now

Copy the Secret immediately and store it securely. You will need it when configuring the Frontegg portal.

Step 7: Add the Confluence API permission

Navigate to the Permissions tab. In the API list, find Confluence API and click Add.

Permissions page with Confluence API row and Add button highlighted

Step 8: Configure Confluence API scopes

After adding the Confluence API, click Configure next to it. On the scopes page, switch to the Granular scopes tab and click Edit Scopes.

Use Granular scopes, not Classic scopes

Frontegg's Confluence integration uses the Confluence v2 REST API, which only accepts granular scopes. Classic scopes (such as read:confluence-content.all) will not work with the v2 API. Make sure you are on the Granular scopes tab before selecting permissions.

In the dialog, select the following scopes:

ScopeDescription
read:page:confluenceView pages
write:page:confluenceCreate and update pages
delete:page:confluenceDelete pages
read:hierarchical-content:confluenceView page descendants and other hierarchical content
read:space:confluenceView spaces
read:space-details:confluenceView space details
write:space:confluenceCreate and update spaces
read:user:confluenceView user details
read:group:confluenceView groups and their members
read:label:confluenceView labels associated with content or spaces
write:label:confluenceAdd and remove labels
read:configuration:confluenceView Confluence settings
read:content-details:confluenceView content details (required for v1 user endpoints)

Click Save.

Edit Confluence API dialog with the 13 granular scopes selected

After saving, the scopes overview shows Scopes Used: 13 with all 13 granular scopes listed.

Confluence API scopes page showing 13 granular scopes configured

Step 9: Configure the callback URL

Navigate to the Authorization tab and click Add next to OAuth 2.0 (3LO).

Authorization tab showing OAuth 2.0 (3LO) row with Add button highlighted

In the Callback URLs field, enter the following URL:

https://YOUR_MCP_GATEWAY_URL/integration-callback

Authorization page with Frontegg callback URLs entered in the Callback URLs field

Click Save changes.

Authorization page after saving, showing the saved callback URLs

Configure the Frontegg portal

Once you have your Client ID and Secret from the Settings page, enter them in the Frontegg portal:

  1. Open the Frontegg portal and navigate to [ENVIRONMENT] → Integrations → Confluence.
  2. Enter the Client ID and Secret in the corresponding fields.
  3. Click Save.

Keep your credentials secure

Never share or commit your Secret to version control.

Additional resources