Skip to main content
This is an updated and improved version of the Confluence connector! If you’re setting up Confluence with ConductorOne for the first time, you’re in the right place.

Capabilities

ResourceSyncProvision
Accounts
Groups
Spaces
Space permissions
To limit sync times, a limited list of Spaces entitlements and their associated grants are synced. See the Spaces entitlements synced by default section of this page for more information.

Gather Confluence credentials

Configuring the connector requires you to pass in credentials generated in Confluence. Gather these credentials before you move on.
ImportantA user with Administrator access in Confluence must perform this task.

Create an API token

1
Log into your Confluence account with Administrator access.
3
Click Create API token.
4
Give your token a label, such as ConductorOne, and click Create.
5
Carefully copy and save the newly generated API token.
That’s it! Next, move on to the connector configuration instructions.

Configure the Confluence connector

To complete this task, you’ll need:
  • The Connector Administrator or Super Administrator role in ConductorOne
  • Access to the set of Confluence credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
1
In ConductorOne, navigate to Admin > Connectors and click Add connector.
2
Search for Confluence v2 and click Add.
3
Choose how to set up the new Confluence connector:
  • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
  • Add the connector to a managed app (select from the list of existing managed apps)
  • Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed. If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Enter your Confluence domain (the URL of your Confluence instance is <YOUR DOMAIN>.atlassian.net) into the Confluence site domain field.
8
Enter the username for your Confluence account in the Username field.
9
Paste the API token into the API key field.
10
Optional. If want to sync information on Confluence users’ personal spaces and their permissions, uncheck the Skip syncing personal spaces and their permissions box.
11
Click Save.
12
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Confluence connector is now pulling access data into ConductorOne.

Spaces entitlements synced by default

Each Confluence Space has its own set of permissions and allowed actions, which can result in a very large set of entitlement and grant access information in each Space. In order to reduce sync times, the Confluence connector only syncs a limited set of Spaces entitlements. By default, the Confluence connector syncs entitlements formed by valid pairs of the following targets (nouns) and operators (verbs), such as administer-space or create-page. Default targets (nouns):
  • attachment
  • blogpost
  • comment
  • page
  • space
Default operators (verbs):
  • administer
  • archive
  • create
  • delete
  • export
  • read
  • restrict_content
  • update
Not all target-operator (noun-verb) pairs are valid. To change or limit what the Confluence connector syncs to ConductorOne, use the --noun and --verb flags when setting up the Confluence connector in self-hosted mode. See the baton-confluence repo’s README for more information.