looker.com or looker.app address.
Looker Studio (formerly Google Data Studio) is a different product. This integration doesn’t connect to Looker Studio, and access to Looker Studio reports isn’t covered by it.
What Oleria discovers
Once connected, Oleria continuously discovers and maps the following from your Looker instance:- Accounts - every Looker user, with name, email address, and when the user last signed in. Disabled users are shown as disabled. Users with a verified two-factor authentication device are shown with multi-factor authentication (MFA) required. Users with a two-factor credential that’s enabled but not yet verified are shown with MFA enrollment required. Users who sign in through SAML, OpenID Connect, Google, LDAP, Looker OpenID, or workforce identity federation are shown with single sign-on (SSO) configured. Embed users and Looker support employees are shown as external users. Users who hold a role with admin permissions are marked as administrators.
- Non-human identities (NHIs) - Looker service accounts, the API keys Looker returns for each user and service account (each shown as a credential owned by the user or service account it belongs to), and the OAuth client apps registered on the instance. For each OAuth app, Oleria shows the users who activated it, because the app acts in Looker on their behalf. Oleria never sees an API key’s secret.
- User groups - every group, its direct members, and the groups nested inside it. Groups mirrored from your identity provider are marked as synced groups. Groups that Looker adds every new user to, such as All Users, are shown as built-in groups.
- Roles - every role, with its permission set and model set, and the users and groups that hold it.
- Activity - events from Looker’s System Activity: sign-ins, failed sign-ins, sign-outs, and administrative changes to users, groups, roles, API keys, and OAuth apps, including sessions where an admin acted as another user. Oleria keeps every other System Activity event too, under its Looker event name.
- AI agents - when agent discovery is enabled for your workspace, the Conversational Analytics agents on your instance. See AI agents.
Oleria doesn’t import dashboards, Looks, folders, database connections, or the access to them. It imports LookML models and Explores only as the data sources of AI agents, when agent discovery is enabled, and not the access to them. This integration covers identity and access governance only.
Prerequisites
- A Looker service account or user for Oleria to connect as, with the Admin role, held directly or through a group. Looker returns the API keys, service accounts, and OAuth apps of other users only to admins, and every remediation action needs admin permissions, so Oleria refuses the credentials of a user without them. Admin permissions also include reading System Activity.
- Admin access to Looker, to create the service account and its API key.
- A Looker instance at a
looker.comorlooker.appaddress. See Known limitations. - If your Looker instance restricts access with an IP allowlist, Oleria’s IP addresses added to it. Contact support@oleria.com for the current list. Otherwise Looker refuses Oleria’s sign-in.
- Admin access to the Oleria workspace.
Create an API key in Looker
1
Create or open a service account
In Looker, go to Admin -> Users. Open the service account Oleria will connect as, or select Add -> Service Account to create one, and give it the Admin role.
2
Create the API key
On the service account’s Edit User page, in the API Keys section, select Manage, then Create New API Key.
3
Copy the credentials
Copy the client ID and the client secret.
The exact location of these settings can change over time. If the steps above don’t match what you see, refer to Looker’s own documentation.
Connect Looker to Oleria
1
Find Looker in Oleria
Go to your Oleria workspace, select Integrations, select the Available tab, and search for Looker.
2
Complete the connection form
Select the Looker card and fill in the form:
3
Authenticate
Select Authenticate. Oleria signs in with the API key and checks that its user has admin permissions before it saves the connection.
Verify the integration
Confirm the Looker instance appears on the Connected tab of your Oleria Integrations page with a status of Healthy. After the first sync completes, check that users, groups, and roles appear in your Oleria workspace. System Activity events appear after the first activity sync.When you edit the integration, you can change the client ID and client secret, for example to rotate the API key, and select Update. Leave Client secret blank to keep the stored secret. If you change the client ID, enter its client secret too. You can’t change the instance URL. To connect a different Looker instance, add a new integration.
AI agents
When agent discovery is enabled for your workspace, Oleria discovers the Conversational Analytics agents on your Looker instance and shows them in the Agents inventory. To enable agent discovery, contact support@oleria.com. Looker offers agents only when a Looker admin has turned on the Gemini in Looker setting and its Conversational Analytics setting for the instance. If Looker refuses Oleria’s request for agents, Oleria shows no Looker agents, and the rest of the sync still completes. Agent discovery needs no permission beyond the admin permissions in Prerequisites.What Oleria discovers about agents
If Looker refuses Oleria’s request for one agent’s content access, that agent is shown without the users and groups it’s shared with.
Remediation actions
Beyond discovery, Oleria can act on Looker access to remediate risk. Every action needs the Admin permissions described in Prerequisites.
Keep these limits in mind when you use these actions:
- Oleria reads the user, group, role, or identity before it changes anything. If it no longer exists in Looker, the action fails. The exception is Remove user from role: Oleria reads the user’s roles, not the role itself, so if the role was deleted in Looker, the action succeeds with no change. If it’s already in the requested state, Oleria makes no change and the action succeeds. For example, Revoke user session tokens succeeds without a change for a user with no open web sessions.
- If Looker returns an error but the target still ends up in the requested state, the action succeeds.
- Reverting an action undoes only the change that action made. When Oleria can’t tell whether a change was made by the action or by someone else in Looker, it doesn’t revert the change if the revert would give access back, such as re-enabling a user or service account, re-adding a membership, or re-enabling an OAuth app, and it doesn’t revert Create user or Create group. Undo the change manually in Looker if needed.
- Oleria won’t disable, delete, or revoke the sessions of the connection’s own user or service account, or change its groups or roles, because that could disconnect the integration.
- Oleria won’t create a user whose email address, or a group whose name, already exists in Looker.
- Groups mirrored from your identity provider, and roles of users whose roles your identity provider manages, can’t be changed from Oleria. Change them in your identity provider. Oleria also can’t add a user to a group when the user’s SSO settings don’t allow direct group membership, or change the roles of a user whose SSO settings don’t allow directly assigned roles.
- Remove user from role removes only the direct assignment. If the user also holds the role through a group, the role stays in effect, and Oleria notes this on the action. If the user holds the role only through a group, the removal fails. To remove it, remove the user from the group, or the group from the role.
- Remove user from group works the same way. If the user also belongs to the group through a nested group, Oleria removes the direct membership and notes that the user is still a member. If the user belongs only through a nested group, the removal fails. Remove the user from the nested group instead.
- To stop an API key, disable the user or service account it belongs to.
- Oleria can’t change permission sets or model sets.
Known limitations
- API keys of standard users. Oleria shows a standard user’s API keys only when Looker’s user API returns them to the connection’s admin. Starting with Looker 26.8 for Looker (original) and Looker 25.18 for Looker (Google Cloud core), admins can no longer manage standard users’ API keys. A standard user whose API keys Looker doesn’t return is shown without API access.
- No account creation date or password change date. Looker’s API doesn’t report when a user was created or last changed their password. User creation appears as activity.
- No last-activity date for API keys, service accounts, or OAuth apps. Looker doesn’t report when an API key was last used, and service accounts sign in only with API keys, so Oleria can’t flag a dormant non-human identity from its account data.
- Instance-wide two-factor enforcement isn’t shown. Looker’s API doesn’t report whether two-factor authentication is required for the instance.
- Embed secrets aren’t inventoried. Looker’s API can create and delete embed secrets but can’t list them.
- Activity history is limited to 90 days. Oleria reads at most the last 90 days of events. Looker trims its event log to the most recent 1 million events, so a busy instance can hold less.
- API call quotas. Each sync uses API calls for every group and role, and every Activity sync runs System Activity queries, with the first 90-day import using the most. Looker (Google Cloud core) Standard edition’s monthly quotas can run out within days. Check your edition’s quotas before connecting.
- Looker-hosted instances only. Oleria connects only to
looker.comandlooker.appaddresses on the standard HTTPS port. Older instances that serve the API only on port 19999, and customer-hosted Looker deployments, aren’t supported. - Custom domains and private IP addresses aren’t supported. A Looker (Google Cloud core) instance reachable only through a custom domain or a private IP address can’t be connected.

