Confluence
What it indexes
The Confluence connector indexes pages, page comments, and supported attachments from Confluence Cloud or Confluence Server and Data Center. Page and attachment hierarchy is retained for navigation and retrieval.
Choose exactly one scope in the connector form:
CQL must return only page objects. Do not add a lastmodified filter because the connector owns update-window filtering. Unsupported or oversized attachments, and images when image processing is disabled, can be skipped.
Prerequisites
- An OpenCore Admin must know whether the source is Confluence Cloud or Server and Data Center and must have the correct wiki base URL.
- The credential must be able to read every selected space, page, comment, attachment, user, group, and restriction needed by the chosen access mode.
- Confluence Cloud OAuth requires
OAUTH_CONFLUENCE_CLOUD_CLIENT_ID,OAUTH_CONFLUENCE_CLOUD_CLIENT_SECRET, a correctWEB_DOMAIN, and the deployment’s OAuth state store. - OAuth is implemented for Confluence Cloud only. Server and Data Center use a manually created personal access token credential.
- For source-permission sync on Confluence Data Center 9.1 or later, use an account that can read REST space permissions; current validation treats the required administrator access as mandatory.
Credentials
Enable Using scoped token only for a scoped Confluence token. That mode adjusts the API URL and authentication path and uses the compatible spaces endpoint.
Configure in OpenCore
- In the Admin panel, open Connectors, choose Confluence, and create or select the credential.
- Set Is Cloud correctly. OAuth credentials lock this value to Cloud.
- Enter the wiki base URL, such as
https://<TENANT>.atlassian.net/wikifor Cloud. - Enable Using scoped token only when the manual token is scoped.
- Select Everything, Space, Page, or CQL Query and complete only that scope’s fields.
- Choose the document access mode your deployment supports, set refresh and pruning options, and create the connector.
- Run the initial index attempt and review skipped attachments or permission failures.
Permissions
Confluence source-permission sync is a conditional deployment capability. When Auto Sync Permissions is available and selected, OpenCore can resolve space permissions, page and ancestor restrictions, users, and groups. Cloud OAuth requests read scopes for content, permissions, users, groups, attachments, search, and offline access.
When source-permission sync is unavailable or not selected, Confluence restrictions are not enforced automatically in OpenCore search. Use Private with explicitly assigned OpenCore user groups for restricted knowledge, or Public only when all OpenCore accounts may see the indexed pages and attachments.
Verify
- Confirm credential probing finds at least one accessible space.
- Run an index attempt and verify pages from the selected scope appear.
- Check that a page comment and a supported attachment are searchable when present.
- Confirm a page outside the selected space, page subtree, or CQL result is absent.
- If Auto Sync Permissions is selected, test both an allowed and a restricted Confluence user.