Overview

The Confluence Cloud connector for Gemini Enterprise provides access to your Confluence Cloud data, allowing you to interact with your spaces, pages, and user information.

Supported Confluence Cloud versions

The Confluence Cloud connector supports Confluence REST API versions v1.

Required scopes

To enable Gemini Enterprise to perform search and data ingestion using the Confluence Cloud data store, you need the following scopes:

Usage reason Permission Description
Data ingestion read:content-details:confluence Allows the connector to read content details in Confluence.
read:content.metadata:confluence Allows the connector to read content metadata.
read:space:confluence Allows the connector to read spaces.
read:whiteboard:confluence Allows the connector to read whiteboards.
read:attachment:confluence Allows the connector to read attachments.
Federated search search:confluence Allows the connector to perform search queries in Confluence.

For information on how to configure these scopes, see Enable OAuth 2.0 and configure scopes.

Rate limits for data ingestion

The Confluence Cloud connector supports a default rate limit of 20 queries per second (QPS) for data ingestion. These rate limits apply exclusively to the ingestion of data from the Confluence Cloud connector.

Limitations

This section outlines known issues and limitations that may affect your use of the Confluence Cloud connector.

  • The Confluence Cloud data store is supported only in Global, US, and EU locations.

  • When creating a new application or adding a data store to an existing application, we recommend that you add a data store with actions belonging to a single connector type. For example, don't associate two Confluence Cloud data stores with actions enabled to the same application.

The following are the limitations for the Confluence Cloud federation connector:

  • Enforcing a VPC Service Controls perimeter on existing Confluence Cloud data stores is not supported. To enforce VPC Service Controls, you must delete and recreate the data stores. For more information on VPSC and how to use actions after enabling VPC Service Controls, see Secure your app with VPC Service Controls.

The following are the limitations for the Confluence Cloud ingestion connector:

  • The legacy user management model is not supported for integration with Confluence Cloud. Only the centralized user management model is supported. For more information, see Atlassian organization consolidation guide
  • The appearance of the macros that you added on Confluence pages might differ from user to user based on their access permissions.
  • The connector doesn't support incremental sync for the spaces entity.
  • You can't use a Google Cloud service account to authenticate to Confluence Cloud.
  • The connector doesn't include archived pages in a full sync operation, and those pages are indexed as deleted.
  • The connector doesn't support spaces and entities shared using anonymous access, guest links, or public URLs.

What's next