Introduction
Connect Confluence spaces so page content becomes searchable knowledge in Docebo.
This connector syncs whole Confluence spaces, page content and hierarchy, rather than individual files, which is why it's listed as a "Sites" connector. That's the key difference from the SharePoint and Google Drive connectors.
1. Basic information
What content gets synced
| Content type | Status | Note |
|---|---|---|
| Published pages within a selected space | Synced | |
| Page labels | Synced | |
| Files and attachments inside pages | Not synced | Out of scope — this connector only covers page content, not files |
| Comments | Not synced | |
| Draft or unpublished pages | Not synced | |
| Archived spaces | Not synced |
What content gets extracted
| Content | Status |
|---|---|
| Page title and body text | Extracted |
| Space name, key, and page URL | Extracted |
| Metadata and page hierarchy (parent/child structure, timestamps) | Extracted |
| Page labels | Extracted |
| Inline images, diagrams, and rendered macro output | Not extracted |
| Comments | Not extracted |
| Page history and version comparisons | Not extracted |
| Attachment file contents | Not extracted |
2. Prerequisites in the source system
Required role
You need an Atlassian organization admin — a Confluence site admin is not enough. Organization admin access is what lets the connector correctly identify users and reach every space; a site admin can't guarantee either.
Required settings
- This connector only supports Confluence Cloud. Confluence Data Center isn't supported.
- If your organization uses an app allowlist, add the new OAuth app to it before authorizing.
3. Preparation in the source system
Create the app
Go to the Atlassian Developer Console, select Create → OAuth 2.0 integration, and name the app (for example, "Docebo Knowledge Connector"). Choose an access type: use Account-level in most cases — it grants access to every site in the customer's Atlassian organization. Only choose Resource-level if the organization has several separate sites and you specifically want to connect just one of them.
Create a new OAuth 2.0 (3LO) integration, with the access type choice.
Add permissions
Open the app → Permissions, and add both the User identity API and the Confluence API. For the Confluence API, add the scopes from both the Classic scopes and Granular scopes tabs — Docebo's connector uses both.
User identity API
| Scope name | Description | Code |
|---|---|---|
| View active user profile | View the profile details for the currently logged-in user. | read:me |
| View user profiles | Required to view users profiles. | read:account |
User identity API — scopes selected in the Atlassian Developer Console.
Confluence API — Classic scopes
| Scope name | Code |
|---|---|
| Read Confluence space summary | read:confluence-space.summary |
| Read Confluence content properties | read:confluence-props |
| Read Confluence detailed content | read:confluence-content.all |
| Read Confluence content summary | read:confluence-content.summary |
| Search Confluence content and space summaries | search:confluence |
| Read content permission in Confluence | read:confluence-content.permission |
| Read user | read:confluence-user |
| Read user groups | read:confluence-groups |
| Download content attachments | readonly:content.attachment:confluence |
Confluence API — Classic scopes tab in the Atlassian Developer Console.
Confluence API — Granular scopes
| Scope name | Code |
|---|---|
| View detailed contents | read:content:confluence |
| View content details | read:content-details:confluence |
| View space details | read:space-details:confluence |
| View pages | read:page:confluence |
| View groups | read:group:confluence |
| View user details | read:user:confluence |
| View spaces | read:space:confluence |
| View space properties | read:space.property:confluence |
| View space settings | read:space.setting:confluence |
| Check content permissions | read:content.permission:confluence |
| View content restrictions and space permissions | read:permission:confluence |
| Read Email Address | read:email-address:confluence |
Confluence API — Granular scopes tab in the Atlassian Developer Console.
Configure authentication
Open Authorization, enable OAuth 2.0 (3LO), and set the Callback URL. The callback URL always follows this pattern: https://[YOUR-DOCEBO-PLATFORM-URL]/knowledge/v1/integrations/connections/callback — for example, https://demo.docebosaas.com/knowledge/v1/integrations/connections/callback. Select Save changes.
Authorization tab with the Callback URL field and the Authorization URL generator.
Define distribution
Open Distribution, and set Distribution status to Sharing — this is what allows any Atlassian account to authorize the connector, not just the one that created the app. Fill in the vendor and security details it asks for: vendor name, privacy policy URL, terms of service URL, and a customer support contact. Under Personal data declaration, answer whether the app stores personal data, then select Save changes.
Edit distribution controls, with Sharing selected and vendor details filled in.
4. Required actions in Docebo
| Information to enter | Where to find it |
|---|---|
| Confluence site URL | Your Confluence Cloud address, e.g. yourcompany.atlassian.net |
| Client ID | Atlassian Developer Console → app → Settings → Authentication details |
| Client secret | Atlassian Developer Console → app → Settings → Authentication details |
Authorizing the connector
- Go to Add-ons and integrations → Knowledge Connectors → Create → Confluence. This menu is only visible to Superadmins.
- Enter the Confluence URL (for example, https://yourcompany.atlassian.net), then select Continue.
Connect Confluence — Setup tab with the Confluence URL field.
- Enter the Client ID and Client secret from your Atlassian app (Settings → Authentication details), then select Authenticate.
Connect Confluence — Authenticate tab with the Client ID and Client secret fields.
- In the Atlassian pop-up, review the requested access and select Accept.
Atlassian consent screen for the Docebo connector.
- On the Scope tab, select which spaces you want available to add to Knowledge collections later, then save your selection.
Connect Confluence — Scope tab for selecting spaces to sync.