Overview

The Confluence Cloud data store 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 data store supports Confluence REST API versions v1.

Supported actions

When the Confluence Cloud data store is enabled, end users can use natural language commands in Gemini Enterprise to perform the following actions.

Action Description
Create page Creates a new Confluence page in a specified space with content and a title.

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
Federated search and actions search:confluence Allows the data store to perform search queries in Confluence.
write:page:confluence Allows the data store to create pages in Confluence.
write:confluence-content Allows the data store to write content in Confluence.
Federated search only search:confluence Allows the data store to perform search queries in Confluence.
Data ingestion and actions read:content-details:confluence Allows the data store to read content details in Confluence.
read:content.metadata:confluence Allows the data store to read content metadata.
read:space:confluence Allows the data store to read spaces.
read:whiteboard:confluence Allows the data store to read whiteboards.
read:attachment:confluence Allows the data store to read attachments.
write:confluence-content Allows the data store to write content in Confluence.
write:page:confluence Allows the data store to create pages in Confluence.
Data ingestion only read:content-details:confluence Allows the data store to read content details in Confluence.
read:content.metadata:confluence Allows the data store to read content metadata.
read:space:confluence Allows the data store to read spaces.
read:whiteboard:confluence Allows the data store to read whiteboards.
read:attachment:confluence Allows the data store to read attachments.

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

Rate limits for data ingestion

The Confluence Cloud data store 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 data store.

Limitations

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

  • When creating a new application or adding a data store to an existing one, we recommend adding only one data store with actions belonging to a single connector type, regardless of the connection mode. For example, don't associate two Confluence Cloud data stores with enabled actions to the same application.
  • 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 VPC Service Controls and how to use actions after enabling VPC Service Controls, see Secure your app with VPC Service Controls.
  • The Confluence Cloud data store is supported only in Global, US, and EU locations.

The following are the limitations for the Confluence Cloud ingestion data store:

  • 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 data store doesn't support incremental sync for the spaces entity.
  • You can't use a Google Cloud service account to authenticate to Confluence Cloud.
  • The data store doesn't include archived pages in a full sync operation, and those pages are indexed as deleted.
  • The data store doesn't support spaces and entities shared using anonymous access, guest links, or public URLs.

What's next