This documentation page describes how to administer Gemini in Looker for a Looker (original) instance. It covers the following topics:
- Different configurations of Gemini in Looker features that are available in Looker (original)
- How to enable and disable Gemini in Looker for a Looker (original) instance
- The permissions that are required to use Gemini in Looker, and how to grant them
This page is intended for users who are assigned the Looker Admin role for the Looker (original) instance.
What is Gemini in Looker?
Gemini in Looker is a product in the Gemini for Google Cloud portfolio that provides generative AI-powered assistance to help you analyze and gain valuable insights from your data. Gemini in Looker can provide assistance for tasks in Looker (original) instances, in Looker (Google Cloud core) instances, and in Looker Studio.
Learn how and when Gemini for Google Cloud uses your data.
For more information about the types of tasks that Gemini in Looker can assist with, see the Gemini in Looker overview documentation page.
Gemini in Looker feature availability
The availability of Gemini in Looker features is summarized in the following table. Depending on the needs of your organization, you can enable the settings that grant users access to the Gemini in Looker features that are available in the appropriate Looker platform.
Accessible Gemini in Looker features | Implementation |
---|---|
|
|
|
Before you begin
To enable or disable Gemini in Looker and to grant users permissions to use Gemini in Looker features, you must be assigned the Looker Admin role for the Looker (original) instance.
To support Gemini in Looker, the following requirements must be met:
- The Looker instance must be on Looker 25.0 or higher
- The Looker instance must be Looker-hosted
Enabling and disabling Gemini
To enable Gemini in Looker, follow these steps:
- In the Admin panel, navigate to the Platform section and select the Gemini in Looker page.
- Under Gemini in Looker enablement, turn on the Enable Gemini in Looker setting. When this setting is enabled, users can access the Gemini in Looker features that are available as described in the Gemini in Looker feature availability table.
- Select Enable Trusted Tester Features. When this setting is enabled, users can access the Trusted Tester capabilities of Gemini in Looker. This setting must be enabled to allow users to access Gemini during the pre-GA preview.
- Optionally, select Enable Trusted Tester Data Use. When this setting is enabled, you consent to your data being used by Google as described in the Gemini for Google Cloud Trusted Tester Program terms. This setting can be enabled only when the Enable Trusted Tester Features setting is enabled. This setting is enabled automatically when the Enable Trusted Tester Features setting is enabled.
- Optionally, select Enable Code Interpreter. When this setting is enabled, users can access the Code Interpreter in Conversational Analytics. This setting can be enabled only when the Enable Trusted Tester Features setting is also enabled. The Enable Code Interpreter setting was enabled by default for Looker (original) instances that had the Enable Gemini in Looker and Enable Trusted Tester Features settings turned on prior to being updated to Looker 25.8 and had been updated to Looker 25.8 on the first day of release deployments.
To disable Gemini for a Looker (original) instance, clear the Enable Gemini in Looker setting.
You must grant the appropriate permissions to users before they can use Gemini in Looker features, including the Code Interpreter.
Grant the Gemini in Looker permission to users
To grant Looker users the ability to use Gemini in Looker features in your Looker instance, you must assign them a role that applies the gemini_in_looker
permission to the appropriate models. You can do this in any of the following ways:
- Grant users the Gemini default role
- Grant users a custom role that contains the
gemini_in_looker
permission - Grant users Conversational Analytics permissions, permission sets, or roles
- Add them to the Gemini Default Users group
Granting the Gemini default role
The gemini_in_looker
permission is the only permission that is included in the Gemini default role, which by default applies to all models on the instance. You must also assign the access_data
permission and any other permissions that may be necessary to use the specific Gemini in Looker feature.
You can assign this role to the appropriate users or groups.
Granting a custom role
To restrict users from accessing Gemini in Looker features for all models on the Looker instance, you can create a custom Looker role that applies the gemini_in_looker
permission for specific models only, and assign it to the appropriate users or groups. You may need to remove those users from the Gemini Default Users group, which is assigned the Gemini default role by default. You must also assign the access_data
permission and any other permissions that may be necessary to use the specific Gemini in Looker feature.
Granting Conversational Analytics roles or permissions
The Conversational Analytics Agent Manager role consists of the Conversational Analytics Agent Manager permission set for all models on the Looker instance. Users with this role can create, edit, share, and delete Conversational Analytics data agents that use Looker Explores.
The Conversational Analytics User role consists of the Conversational Analytics User permission set for all models on the Looker instance. Users with this role can chat with any Conversational Analytics data agent in Looker.
You can assign either of these roles to the appropriate users or groups. You can also create a custom Looker role that applies any of the Conversational Analytics permissions to specific models.
Adding users to the Gemini Default Users group
The Gemini Default Users group has been created automatically for all Looker (original) instances that use an open system configuration. Users in this group are assigned the Gemini role, which grants them the ability to use Gemini in Looker features when they also have a role that includes the other required permissions to use Gemini in Looker features.
You can edit the Gemini Default Users group to add or remove users, or to delete the group entirely. You can also add additional roles to the group.
For more information about how users are added to this group, see the Groups documentation page.
Additional permissions
The following Gemini in Looker features require additional permissions:
- To create custom visualizations with Gemini assistance, you must be assigned a Looker role that contains the
can_override_vis_config
permission. - To write LookML with Gemini assistance, you must be assigned a Looker role that contains the
develop
permission for at least one model in a LookML project. - To query Looker data, or to create a data agent with Conversational Analytics or with the Conversational Analytics API, you must be assigned a Looker role that contains the
access_data
permission for the model that you are querying. Additional permissions are required to manage and use data agents with Conversational Analytics in Looker.
Provide feedback
You can provide feedback about each Gemini in Looker feature. Instructions for how to submit feedback are included in the documentation for each feature.