Set up a Linear data store

This page describes how to create a data store and connect Linear to Gemini Enterprise.

Before you begin

Before you set up your Linear data store, do the following:

  1. Grant the Discovery Engine Editor role (roles/discoveryengine.editor). This role is required for the user to create the data store. To grant this role, do the following:

    1. In the Google Cloud console, go to the IAM page.

      Go to IAM

    2. Locate the user account and click the edit Edit icon.
    3. Grant the Discovery Engine Editor role to the user. For more information, see IAM roles and permissions.

  2. To enforce data source access control and secure data in Gemini Enterprise, ensure that you have configured your identity provider.

  3. Create an app in the Linear API settings and obtain the authentication credentials. For more information, see Linear configuration.

Create the Linear data store

To create a Linear data store, do the following:

  1. In the Google Google Cloud console, go to the Gemini Enterprise page.

    Gemini Enterprise

  2. Select or create a Google Cloud project.

  3. In the navigation menu, click Data stores.

  4. Click Create data store.

  5. On the Select a data source page, enter Linear into the search field. The Linear card displays.

  6. Click Select.

  7. In the Data section, fill in the following fields:

    1. Under Authentication settings, enter the values you copied when you created an app in the Linear API settings:

      • For Client ID, enter the Linear app's Client ID.

      • For Client Secret, enter the Linear app's Client secret.

      For more information about creating an app in the Linear API settings, see Linear configuration.

    2. Click Login.

    3. Click Continue.

    4. In the Entities to search section, select the entity types that you want Gemini Enterprise to search. You can select from the following types:

      • Issue

      • Project

      • Team

      • Comment

    5. Click Continue.

  8. In the Actions section, select the actions that you want users to be able to perform in their Linear accounts using the Gemini Enterprise assistant.

    To manage the list of actions, see Manage actions.

  9. In the Configuration section:

    1. From the Multi-region list, select the location for your data connector.
    2. In the Your data connector name field, enter a name for your connector.
    3. If you selected US or EU as the location, configure the Encryption settings:
      • Optional: If you haven't configured single-region keys, click Go to settings page to do so. For more information, see Register a single-region key for third-party connectors.
      • Select Google-managed encryption key or Cloud KMS key.
      • If you selected Cloud KMS key:
        • In the Key management type list, select the appropriate type.
        • In the Cloud KMS key list, select the key.
      For more information, see Customer-managed encryption keys.

  10. Click Continue.

  11. In the Billing section, select General pricing or Configurable pricing. For more information, see Verify the billing status of your projects and Licenses.

On the Data Stores page, click your data store name to see the status. After the data store state changes from Creating to Active, the Linear data store is ready to be used.

Data handling and query execution

This section describes how Gemini Enterprise manages your query and the privacy implications of using the federated data store.

Query execution

After you authorize Linear and send a search query to Gemini Enterprise:

  • Gemini Enterprise sends your search query directly to the Linear API.
  • Gemini Enterprise blends the results with those from other connected data sources and displays a comprehensive search result.

Data handling

When using third-party federated search, the following data handling rules apply:

  • Your query string is sent to the third-party search backend (Linear API).
  • These third parties may associate queries with your identity.
  • If multiple federated search data sources are enabled, the query might be sent to all of them.
  • Once the data reaches the third-party system, it is governed by that system's terms of service and privacy policies.

What's next