Overview

The Concur connector for Gemini Enterprise lets you search and read data across your Concur datasets.

Required permissions

To enable Gemini Enterprise to perform federated search using the Concur data store, you need to enable the following scopes:

Scope Purpose
expense.report.read Allows the app to read expense report headers and details within Concur.
identity.user.core.read Allows the app to read core user profile information.
identity.user.coresensitive.read Allows the app to read sensitive core user profile information.
identity.user.ids.read Allows the app to read unique identifiers of users.
locality.read Allows the app to read details of a locality for a given company.
receipts.read Allows the app to read receipt images, metadata, and status.
user.provision.read Allows the app to read user provisioning and account profile data.

For information on how to configure these scopes, see Set redirect URL and scopes.

Limitations

This section outlines known issues and limitations that may affect your use of the Concur 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 Concur 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 Concur data store is supported only in the global, us, and eu locations.

What's next