The Confluence Cloud data store for Gemini Enterprise lets you search and perform actions on 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. |
| Download attachment | Downloads an attachment from a Confluence page. |
| Upload attachment | Uploads an attachment to a Confluence page. |
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 data store to read content details in Confluence.
read:attachment:confluence
Allows the data store to download and read attachments.
read:comment:confluence
Allows the data store to read comments.
read:page:confluence
Allows the data store to read pages.
read:whiteboard:confluence
Allows the data store to read whiteboards.
read:space:confluence
Allows the data store to read spaces.
read:group:confluence
Allows the data store to read groups.
read:user:confluence
Allows the data store to read users.
read:content.metadata:confluence
Allows the data store to read content metadata.
read:configuration:confluence
Allows the data store to read configurations.
Federated search
search:confluence
Allows the data store to perform search queries in Confluence.
Actions
write:page:confluence
Allows the data store to create pages in Confluence.
write:attachment:confluence
Allows the data store to upload attachments to Confluence pages.
write:confluence-content
Allows the data store to write content in Confluence.
write:confluence-file
Allows the data store to upload attachments to Confluence.
read:attachment:confluence
Allows the data store to download and read attachments.
read:comment:confluence
Allows the data store to read comments.
read:configuration:confluence
Allows the data store to read configurations.
read:confluence-content.all
Allows the data store to read all Confluence content.
read:confluence-space.summary
Allows the data store to read space summaries.
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:group:confluence
Allows the data store to read groups.
read:me
Allows the data store to read current user information.
read:page:confluence
Allows the data store to read pages.
read:space:confluence
Allows the data store to read spaces.
read:space-details:confluence
Allows the data store to read space details.
read:task:confluence
Allows the data store to read tasks.
read:user:confluence
Allows the data store to read users.
search:confluence
Allows the data store 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 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 app or adding a data store to an existing one, it's recommended to associate only one data store with actions belonging to a single connector type.
- 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 the
global,us, andeulocations.
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
- To create and configure a data store with Confluence Cloud, see Set up a Confluence Cloud data store .
