The Confluence connector for Glean allows Glean to fetch and index content from Confluence, ensuring that users can search and access documents for which they have authorized permissions.

API Usage

Integration Features

The Confluence cloud connector has no specific version limitations, which is Atlassian’s SaaS offering of Confluence in the cloud.

Glean also supports Confluence datacenter edition, a customer-managed deployment (not SaaS) with a different Glean connector and separate documentation.

The Confluence connector for Glean supports the following objects:

The connector ensures comprehensive data coverage, including metadata, identity data, permissions data, and activity data. It provides real-time synchronization, reflecting updates and permission changes immediately in search results.

For Confluence Cloud, the Atlassian admin needs to install Glean’s Forge App on the instance. The Admin scope is required to fetch permissions associated with Confluence objects, which is necessary for correctly enforcing permissions in the search experience.

While “read” permissions allow access to all content for the Connector, write:space.permission:confluence scope is necessary for the initial installation to automatically be added to all Confluence spaces. Alternatively, the administrator must manually add the Glean crawler to all spaces.

The Glean connector for Confluence by default, is configured to access all Confluence spaces and pages except Restricted Pages. Atlassian Admins cannot view restricted pages unless the admin user is given explicit access.

Confluence Restricted Pages can be important for users who request to be included in search results. Glean has built the capability to crawl, and index restricted pages in a permissions-enforced way. It involves providing the “Scio Search for Confluence” app view access to the pages to be indexed. The following is an overview of the procedure:

For any of the users who have edit access to their Restricted Pages and need to have those pages crawled and indexed into Glean, they must do the following:

Individual users must authorize Glean in the UI by clicking your profile picture (bottom left corner) → Your settings → Data sources → Confluence Cloud.

For Confluence, Glean crawls the following content:

The identity crawl operates with the following configurations:

Crawls the following activities on content (Spaces, pages, blogs,...) to keep the index current:

The Glean Activity plugin for Confluence helps Glean provide highly personalized search results for users. By sending webhook events to Glean each time a user views a page, blog, or piece of content, the plugin enables Glean instance to gather valuable information crucial to delivering an outstanding search experience. This information is stored securely in your dedicated cloud project (Glean or customer-hosted), ensuring complete privacy and protection of your data.

Content updates for the Confluence connector in Glean can happen quite rapidly, depending on the type of update and the configuration settings. Here are the key areas:

Changes in data must be crawled, processed, and indexed before the data is reflected in the UI. Actual time may vary depending on the number of changes and corpus size. For the most up-to-date crawler refresh information, please refer to [External] Glean crawling strategy

The crawler follows the traditional crawler strategy, including utilizing the API and the following ways to get and update data:

The Confluence connector for Glean has the following known limitations in its crawling process:

Unsupported objects include:

These limitations highlight the constraints and ongoing improvements for the Confluence connector, ensuring better performance and user experience.

Note: If Inclusion (Green-Listing) options are enabled, only content from the Inclusion category will be indexed. If Exclusion (Red-Listing) options are enabled, all content in the exclusion category will be removed. If both rules are applied to the same content, then the content will NOT be indexed, as exclusion rules take priority.

The rules below should be used MINIMALLY to preserve the enterprise search experience, as most end-users expect to find all content. Most customers do not apply any rules or apply exclusion rules sparingly for sensitive folders. Exclusion rules are applied automatically after the next full crawl, which can vary by corpus size. If a recrawl is needed, please reach out to your Glean representative.

Glean provides several options for excluding content from the data crawl, which excludes data from search and chat results.

Glean provides several options for including content from the data crawl, which includes data from search and chat results.

Note: Only content specified to be included items will show in search results, chat, or any other Glean applications. Unspecified content will not be included in search results, chat, or other Glean applications.