Overview

The Box connector for Gemini Enterprise lets you access your Box data and interact with records.

Supported Box versions

The Box connector supports Box API version 2024.0.

Required scopes

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

Connection mode Scope Purpose
Federated search Read all files and folders stored in Box Required to fetch comments and tasks, and to preview files for search.
Data ingestion Read all files and folders stored in Box Required for data ingestion.
Manage users Required to fetch the list of users, enabling retrieval of files, comments, and tasks from individual user accounts for ingestion. The administrator service account does not inherently possess access to all user-owned files. The as-user header enables the system to make API requests as the specific user to access their data.
Manage enterprise properties Necessary for incremental sync functionality, as it facilitates the use of the Enterprise event stream to track changes for ingestion.
Manage groups Required to fetch the list of groups and their members. This is critical for access control during ingestion.

For information on how to add the permissions for Box, see Configure Box and set the necessary permissions.

Limitations

  • The Box federated data store uses Box APIs for search. Consequently, search quality depends on the results provided by Box search. This can result in limitations in search quality for non-English languages, because Box APIs might not be fully optimized for them. To achieve better search quality in these scenarios, use the ingestion data store instead.

  • Enforcing a VPC Service Controls perimeter on existing Box 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 Box data store is supported only in Global, US, and EU locations.

What's next