Confluence Server Connector

1. Key capabilities

• Genly crawls Confluence pages (including parent/child hierarchy), blog posts, labels, attachments, comments, and related data.
• Genly respects all user access permissions so users only see search results for documents they are allowed to access. When a user clicks a search result, they are redirected to the Confluence web application, which enforces permissions.
• The connector uses a hybrid sync model of "full crawl + webhook incremental listening + permission compensation scans." For changes to pages, blogs, attachments, labels, likes, content permissions, space permissions, and user/group relationships, the system can collect and process updates near-real-time after events fire. Content changes continue through parsing and indexing, and search visibility depends on parse, ingest, and index task completion. New or edited comments sync as interaction data attached to pages or blogs and appear in content details, but comment bodies are not independently full-text indexed. Content deleted before it was ever synced cannot be re-fetched from Confluence and can only be cleaned up from historical snapshots.
• All data is stored in the customer's private environment, ensuring no data leaves the customer environment.
• Genly uses Atlassian's standard Confluence REST API to retrieve all data.
• Confluence 6.5 has no native webhook capability. To enable near-real-time sync, Genly provides a proprietary Confluence plugin that listens to Confluence events to deliver webhook functionality.

2. Supported versions

• Supports Confluence Server 6.5. Contact your Confluence administrator for version information.
• Genly plans to support Confluence Data Center/Cloud.

3. Crawl and index scope

The Genly Confluence connector crawls three categories of data—content, identity, and activity—to keep indexes fast, comprehensive, and securely manageable.

3.1 Content

• Crawls pages, blog posts, spaces, attachments, page comments, labels, likes, and related data; indexes pages, blog posts, attachments, and related content.
• Pages keep their original hierarchy; blog posts are organized by year and month. Both are crawled through standard content list APIs.
• If the configured connector account can access restricted pages, those pages can be indexed while search results still enforce permissions.

3.2 Activity data and webhooks

Genly handles create, update, delete, move, and permission-change events for fast updates. The tables below list change events supported by the Genly plugin.

3.2.1 Content events

3.2.2 Space, label, and permission events

3.2.3 User, group, and membership events

3.3 Identity data

• Crawls all Confluence user information, including usernames, account names, and email addresses.
• When Confluence version limitations cause user records to diverge from the identity provider, the Genly admin console also supports manual person matching.

4. Known limitations

• Comments and likes are not indexed, but related comments can be found by searching the commented page or blog.
• Deleted pages, blogs, attachments, spaces, and similar objects cannot be crawled.
• After permissions are revoked, the connector account may no longer read restricted pages, blogs, or attachments. The system can refresh visibility through permission events, but re-fetching body content or attachments may fail if the account lacks access.
• For changes that occurred before deletion but were not delivered by webhook or processed while the connector was offline, the system can only detect differences during the next full crawl or from historical snapshots. If an object was deleted before the full crawl, its content can no longer be fetched.
• After a user, group, or external directory object is deleted, detail APIs may no longer return complete information. Organization sync tries to delete or unlink using usernames, group names, and historical org data from events, but cannot reconstruct full records for objects that no longer exist.

5. Update frequency

In this table, "webhook incremental" means the system starts collecting and processing changes after an event fires—it does not mean users immediately see final search results. Content changes still require file upload, metadata ingestion, parsing, and indexing. Searchable time depends on queue backlog, file size, parse duration, and index service throughput.

6. How crawling works

The crawler follows traditional crawl strategies, using APIs and the approaches below to fetch and update data:

• Identity crawl:Updates and adds people data, including users, accounts, and email information.
• Webhook:Messages sent by the application to notify Genly of changes in near-real-time; Genly then starts a crawl or picks up the change on the next crawl.
• Content crawl:Full crawl of the application's entire defined scope.

7. Required permissions

The user configuring this connector must have administrator permissions. The Confluence account used must have access to the content being synced.

8. Setup

Follow these steps to connect Confluence Server to Genly.

8.1 Create a service account for Genly

1. Sign in to Confluence as an administrator.
2. Go to User management.
3. Create a user with any name, email, and password.
4. Click Edit groups.
5. Add the service account to confluence-administrators.

8.2 Create a Confluence data source

1. In the Genly admin console, create a Confluence data source and enter the server base URL on the setup page—for example, https://confluence.mydomain.com.
2. Enter the username and password created in step 8.1.
3. Click Test connection to verify connectivity to the Confluence instance.
4. Click Save to create the Confluence data source.

8.3 Create a Confluence identity connector

1. In the Genly admin console, open People & Organization and click Sync from other apps.
2. Click Add people sync, choose Confluence, and select the Confluence data source instance in the dialog.
3. Click Create to finish creating the identity connector.

8.4 Install the Confluence plugin and create the Confluence connector

1. In the Genly admin console, open Connectors and click Add connector.
2. Choose Confluence, click Next, and select the Confluence data source instance.
3. On the confirm connection step, click [Plugin] to download the Confluence plugin.

1. In the Confluence admin console, open the plugin management page, upload, and install the Confluence plugin.
2. Confirm that Atlassian WebHooks Genly Plugin is installed and enabled.
3. In the Genly admin console, click Test connection, then Next. Select specific spaces or all spaces in Confluence to sync, check the content types to sync below, and create a flat label taxonomy in Knowledge Labels first if you need label sync.
4. Click Next to finish creating the Confluence connector.

9. Confluence API endpoints