Confluence Server connector

Back to the list of Connectors

The Confluence Server Connector integrates Search AI with your self-hosted Atlassian Confluence Server site, enabling intelligent search over your organization’s knowledge articles. You can authenticate with a Bearer token, Basic credentials, or OAuth 2.0 through an Auth Profile.

Specifications

Specification	Details
Supported content	Pages, blog posts, attachments, and comments
Authentication	Bearer token, Basic, or OAuth 2.0 (through an Auth Profile)
Permission-aware ACL support	Yes
Content filtering	Yes

Prerequisites

• The Platform can access the Confluence Server site.
• Your account has required permissions to read the content types to be indexed. To synchronize permissions, the account must be able to read space permissions, page restrictions, and group membership.
• Platform Auth Profile for the authentication type you plan to use (Bearer token, Basic, or OAuth 2.0). You can create one from the connector page by clicking New auth profile, or beforehand under Project Settings > Auth Profiles.

Connector configuration

To configure the Confluence Server connector, open the connector page and complete the sections below in order.

Connection

Connect a Confluence Server site. Use a Bearer, Basic, or OAuth 2.0 Auth Profile, enter the reachable Confluence URL, and validate the instance before selecting spaces.

Field	Description
Confluence auth profile	The Auth Profile the connector uses to authenticate. Select an existing profile, or click New auth profile to create one.
Auth type	The authentication method of the selected profile. Select Bearer token, Basic, or OAuth 2.0. Bearer token is selected by default.
Confluence base URL	The URL of your Confluence Server site, for example https://confluence.example.com/confluence. Include the context path if your instance uses one.

After you complete these fields:

1. Click Validate connection to confirm that the Platform can reach the instance and authenticate.
2. Click Discover spaces to load the spaces that the account can access into the space picker.

Spaces and filters

Select the content to synchronize and configure content filters. Space keys create the hard source boundary: the connector reads only content in the selected spaces. The optional date, ancestor, and CQL filters narrow what sync reads within those spaces.

Field	Description
Space keys	The keys of the spaces to synchronize, separated by commas, for example ENG, HR, OPS. You can type keys directly or select them with the picker.
Discovered spaces	Shows how many spaces discovery found. Use Select visible to select the spaces shown, Select all discovered to select every discovered space, or Clear to clear the selection.
Search spaces	Filters the discovered spaces by key or name. Run discovery first to load spaces into the picker.
Selected spaces	Lists the selected spaces.
Modified after (Optional)	Synchronize only content modified after this date.
Modified before (Optional)	Synchronize only content modified before this date.
Ancestor page IDs (Optional)	Comma-separated page IDs, for example 123456, 987654. Limits the sync to content under these ancestor pages.
Advanced CQL (Optional)	A Confluence Query Language (CQL) expression that further narrows the content that sync reads.

Objects and child resources

Choose which Confluence objects to synchronize. All the options are turned on by default.

Option	Description
Pages	Primary answer source, with hierarchy, space, ancestor, and version context.
Blog posts	Primary answer source for blog content.
Attachments	Child files tied to the selected pages and blog posts.
Include comments	Collects page and blog comments as parent-linked discussion documents.

Attachment formats

When Attachments is turned on, choose which attachment formats to synchronize.

Option	Description
Default supported	Synchronizes the file formats the Platform supports by default. This is the default selection.
Standard	Synchronizes a standard set of file formats.
Custom	Lets you specify the file formats to synchronize.

Permissions

Configure permission-aware synchronization. When Permission-aware ACL is turned on, the connector synchronizes Confluence space permissions, restrictions, and group membership, and enforces them during search so that users see only the knowledge content they are authorized to access. If the connector cannot prove that a user is allowed to see an item, it hides the item (fail closed).

Permission-aware ACL is turned on by default.

Review and activate

Generate the package proposal, run a bounded dry run, then activate the source when the preview is acceptable.

1. Click Generate proposal to generate a proposal preview of what the connector will synchronize.
2. (Optional) Click Dry run to validate the configuration with a bounded run before starting the initial synchronization.
3. When the preview is acceptable, click Approve & sync to activate the connector and start the initial synchronization.