Atlassian Confluence Legacy Connector
The Coveo Legacy connector for Atlassian Confluence allows Coveo administrators to index and integrate the content of Confluence Wiki sites and spaces into the
Coveo unified index, making it easily searchable by end-users.
Important: The Atlassian Confluence Legacy Connector is now deprecated. To index Atlassian Confluence
content, use the second-generation Confluence connector
![]() |
Confluence Connector Guide |
Connector Features Summary
Features | Supported | Additional information | |
---|---|---|---|
Confluence version |
5.5 to 5.8.5 and Cloud
|
||
Searchable content types |
![]() |
Spaces, pages (such as Wiki pages), blog posts, comments on pages and blog posts (included as metadata), and attachments (in pages, blog posts, and comments) |
|
Content update | Incremental refresh |
![]() |
|
Full refresh |
![]() |
Rebuild needed to apply space name changes (if any) to all space pages. | |
Rebuild |
![]() |
||
Document-level security |
![]() |
|
Features
The Confluence connector features are:
-
Extraction and indexing of all Confluence item types:
-
Spaces
-
Wiki pages
-
News items (blog posts)
-
Comments
-
Attachments (binary documents)
-
-
Extraction and indexing of document permissions (supports LDAP integrations, including Active Directory).
-
Extraction and indexing of labels.
-
Supports the Confluence security model by indexing document permissions (for on-premises deployments when the plugin is installed) so that in Coveo search interfaces, a user searching Confluence content only sees the content to which he has access in Confluence.
Note: The Coveo search interface includes a Quick View of Confluence content and provides Confluence specific facets based on spaces, object types (Page, Comment...), and labels.
Limitations
-
The Confluence connector does not support incremental refresh. A source full refresh is required to update the source content.
-
If you change the name of a space in Confluence, a full refresh detects the change only for pages created or modified following the change. You must rebuild the source to get the space name change on all space pages.
What's Next?
Review the steps to deploy the Confluence connector (see Atlassian Confluence Legacy Connector Deployment Overview).