> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/business-intelligence/looker-integration/using-a-custom-looker-role.md). # Using a custom Looker role Some teams prefer to use custom [Looker roles](https://cloud.google.com/looker/docs/admin-panel-users-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

2. Click "New Model Set"

3. 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. 4. Click "New Model Set" to save the new Model Set.

5. 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.

### Stage 2: Create a Permission Set 1. In the "Roles" screen, click "New Permission Set"

2. 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. 3. Click "New Permission Set" to save the new Permission Set

4. Verify that the new Permission Set was created in the Permission Sets table in the "roles" screen.

### 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"

3. Verify that the role is created in the "Roles" tables

### Stage 4: Create a Looker User and assign it the Looker Role 1. Find the "Users" option in the "admin" sidebar

2. Click "Add Users"

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

You're done. Go back to [stage 1 in Setting up Euno's Looker Integration](/sources/business-intelligence/looker-integration.md#stage-1-create-a-looker-api-key-to-be-used-by-euno-to-access-lookers-api) and follow the steps there. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.euno.ai/sources/business-intelligence/looker-integration/using-a-custom-looker-role.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.