For the complete documentation index, see llms.txt. This page is also available as Markdown.

Using a custom Looker role

Some teams prefer to use custom Looker roles to configure Euno's Looker integration. Consider using a custom Looker Role for Euno's Looker integration to:

  1. Further lock down the permissions of Euno's Looker integration

  2. Avoid breaking Euno's Looker integration when configuring permissions for other Looker users

Setting up a Custom Role for Euno's Looker Integration

To set up a custom Looker Role for Euno's Looker integration complete the following:

  1. Create a Looker Model Set

  2. Create a Permission Set with the minimal permissions required

  3. Create a Looker Role

  4. Create a Looker User and associate it with the Looker Role

Stage 1: Create a Looker Model Set

  1. Browse to the "admin" section in your Looker instance and find the "roles" menu item

Looker: Admin Settings - Roles
  1. Click "New Model Set"

Looker: New Model Set
  1. Name the new Model Set euno_model_set. Do not check any of the LookML models. Euno's Looker integration does not require access to any LookML model, except to discover LookML dashboards (see Discovering LookML dashboards).

  2. Click "New Model Set" to save the new Model Set.

Looker: Save New Model Set
  1. Once saved, you'll be redirected back to the "Roles" screen. Verify that the model set was created by scrolling down to the "Model Sets" table. You should see the new Model Set there.

Looker: Model Sets Table

Stage 2: Create a Permission Set

  1. In the "Roles" screen, click "New Permission Set"

  1. Name the new Permission Set euno_permission_set and check the following permissions:

  • access_data

  • manage_models

  • see_users

  • see_system_activity

see_users is required when Observe users or Observe groups are enabled in Euno (they are enabled by default). see_system_activity is required for source validation and usage observation.

Discovering LookML dashboards

Euno discovers LookML dashboards through the Looker API when the Euno user can read them, and otherwise from their files in the LookML Git repository, when Euno can read it. Looker lets a user read a LookML dashboard only when the user's role has see_lookml_dashboards and access to the model that includes the dashboard. With the minimal role above, Looker does not let the Euno user list dashboards at all, so Euno discovers LookML dashboards only from the repository, and the integration's run report says so.

A LookML dashboard discovered from the repository is always placed in the LookML Dashboards folder, and its tiles have no tile-level usage. To discover LookML dashboards through the Looker API instead, with their actual folders and tile usage, also:

  • check see_lookml_dashboards in euno_permission_set, and

  • check, in euno_model_set, the LookML models whose dashboards Euno should discover.

see_lookml_dashboards and access_data are model-specific permissions, so they apply to the models in euno_model_set. Selecting a model therefore also gives the Euno user access_data on it.

  1. Click "New Permission Set" to save the new Permission Set

Looker: Save Permission Set
  1. Verify that the new Permission Set was created in the Permission Sets table in the "roles" screen.

Looker: Permission Sets Table

Stage 3: Create a Looker Role

  1. Back in the "roles" screen, click "New Role"

  2. Name the role euno_role, pick euno_permission_set and euno_model_set, and click "New Role"

Looker: Create a Looker Role
  1. Verify that the role is created in the "Roles" tables

Looker: Roles

Stage 4: Create a Looker User and assign it the Looker Role

  1. Find the "Users" option in the "admin" sidebar

Looker: Admin Settings - Users
  1. Click "Add Users"

  1. Give the user an email address, assign the role euno_role, then click "Save"

Looker: Assigning Role to User

You're done. Go back to Step 1 in Setting up Euno's Looker source and follow the steps there.

Last updated