> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # Looker > Read Looker Looks and dashboards and run Explore queries live in Hebno, scoped by team and LookML model. Hebno never writes to Looker. The Looker integration brings your governed metrics into client work. Ask how Contoso's basket size moved after the October price change, pull the figures behind a dashboard tile into a readout, or run a new question against an Explore, and Hebno answers from Looker with each Look, dashboard and query cited. Hebno uses your LookML definitions, so a figure in a reply matches the same figure in Looker. Hebno never writes to Looker. ## At a glance | | | | - | - | | **Connection** | Organisation connection, made by an owner or admin with a Looker API user. Members can link their own Looker account. | | **Default access** | Read only. Models marked as financial are visible to owners and admins until you share them with teams. | | **Attach** | Looks, dashboards, dashboard tiles, Explores | | **Search** | Hebno searches Looker when a request mentions a dashboard, Look, metric, dimension, model or Explore | | **Link** | A project links to one or more Looker dashboards or Looks | | **Write** | None. Hebno reads only. | ## Before you start You need: * An owner or admin role in Hebno. * Your Looker instance address, for example `https://northwind.cloud.looker.com`. * A Looker user for the integration, created by a Looker admin under **Admin → Users**. Give it a role whose permission set and model set cover only what Hebno should read. * API credentials for that user. A Looker admin opens the user under **Admin → Users**, selects **Edit Keys** under **API Keys**, then **New API Key**, and copies the **Client ID** and **Client Secret**. Hebno calls the Looker API 4.0 and runs queries with the same row limits and access filters as the Looker interface. The integration user's role needs these permissions: | Looker permission | Why Hebno needs it | | - | - | | `access_data` | Run queries and read results | | `see_looks` | List and read saved Looks | | `see_user_dashboards` and `see_lookml_dashboards` | List and read user-defined and LookML dashboards | | `explore` | Run new queries against Explores in the role's model set | | `see_lookml` | Read field labels and descriptions so Hebno picks the right dimensions and measures | Leave out permissions such as `develop`, `deploy`, `save_content`, `schedule_look_emails` and `manage_models`. Hebno does not need them. ## Connect Looker **1. Allow the integration** Open **Admin → Connectors → Catalogue**, find **Looker** under **Data and analytics**, and set it to **Allow**. **2. Connect the organisation** Select **Connect**, enter the Looker address, **Client ID** and **Client Secret**, then select **Test connection**. Hebno signs in to the Looker API and lists the models and folders the integration user can read. **3. Choose teams and data areas** Under **Who can use it**, choose **All teams** or pick teams. Under **Data areas**, choose which models and content each team can use. See [Data areas](#data-areas). **4. Confirm access** **Access** is **Read only**. Looker has no write actions in Hebno. The card shows **Connected** with the Looker address. Members in the selected teams can use Looker in chat straight away. ### Link your own account Members can link their own Looker account so queries run with their own Looker role, model set, user attributes and access filters. 1. In Hebno, open **Settings → Connections**, find **Looker** and select **Link your account**. 2. Sign in to Looker and select **Allow**. Linking uses Looker's OAuth sign-in for API clients. A Looker admin registers Hebno as an OAuth client app once, with the redirect URI shown on the **Looker** card in **Admin → Connectors**. When your account is linked, you see only the content and rows your Looker access allows. ## Data areas Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of whatever the integration user can read in Looker. | Data area | Includes | Default | | - | - | - | | **Looks** | Saved Looks in folders the integration user can open, with their results | All allowed teams | | **Dashboards** | User-defined and LookML dashboards and their tiles | All allowed teams | | **Explores** | New queries against Explores in the chosen models | All allowed teams | | **Models** | The LookML models each team can query, chosen per team | All models in the model set | | **Financial models** | Models you mark as financial, such as revenue, margin or utilisation models | Owners and admins | ![Admin connector panel showing who can use it, access and data areas](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/org-connection.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=8d965e9c74747db0c182b004d569b236) An organisation connection with team access and data areas. Financial figures default to owners and admins. To share a margin model with delivery leads, open the Looker card in **Admin → Connectors**, select **Financial models** and add the teams that should see it. > [!NOTE] > > When a member has linked their own account, Hebno uses that member's Looker permissions instead of the organisation connection. Data areas still apply, so a member never sees more through Hebno than both Looker and your Hebno settings allow. ## What Hebno reads | Looker object | Fields Hebno uses | Typical questions | | - | - | - | | **Look** | Title, folder, description, model, Explore, fields, filters, results | "What does the weekly basket size Look show for Contoso?" | | **Dashboard** | Title, folder, filters, tiles and the query behind each tile | "Summarise the Contoso pricing dashboard for October." | | **Explore** | Model, Explore name, dimensions, measures, labels and descriptions | "Which Explore has store-level margin?" | | **Query** | Fields, filters, sorts, row limit, results, generated SQL | "Average basket size by region since 1 October, by week" | ![Chat reply citing a Looker dashboard tile](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-looker.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=2bf52578339ba7680b734e615daca470) A Looker dashboard tile attached to a chat. For a new question, Hebno picks the Explore, fields and filters from your LookML, runs the query, and shows them with the reply so you can open the same query in Looker. Results above the row limit are cut off, and the reply says so. Reads are live. Hebno runs each query in Looker when a request needs it and does not copy results into the knowledge index. Only what a reply used is stored with the conversation as its sources. ## Hebno reads only Hebno does not write to Looker. It does not save Looks or dashboards, change LookML, schedule deliveries, or create alerts. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Looker You->>Hebno: How did Contoso basket size move after the October price change? Hebno->>Looker: Find the Explore and fields for basket size by week Looker-->>Hebno: retail model, orders Explore, average basket size Hebno->>Looker: Run the query with client = Contoso, since 1 October Looker-->>Hebno: Weekly results and generated SQL Hebno-->>You: Answer with the query cited and a link to open it in Looker ``` ## Link a project to a dashboard Linking marks which Looker dashboards or Looks belong to an engagement, so you can ask "how are the numbers moving?" without naming the dashboard. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Looker**. 3. Search by dashboard or Look title and select it. Repeat for each one in the engagement. In chats tagged to the project, Hebno starts with the linked dashboards for any figure question. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Looker in chat * **Attach**: open the **+** menu, choose **Sources → Looker**, and pick a Look, a dashboard, a tile or an Explore. Or type `/` and choose **Looker**. * **Ask**: name the metric, dashboard or filter in your request. For example: > Using the Contoso pricing dashboard, which store clusters lost margin in October? > Show average basket size by week for Contoso since 1 September, split by region, and explain the change. > Which Explore should I use for promotion uplift, and what do its measures mean? * **Research runs** show a **Checking Looker** step, with a chip for each Look, dashboard and query it ran. * **Agents** can read Looker on a schedule, for example a Monday brief on the Contoso pricing dashboard. Writes an agent proposes elsewhere appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | **Test connection** fails with **Not found** on login | Check the Looker address, **Client ID** and **Client Secret**. Create a new API key for the integration user if the secret was lost. | | A model or Explore is not found | It is outside the role's model set, or not in the team's **Models** data area. Looker returns not found for content the user cannot see. | | A query returns no rows that Looker shows to you | An access filter on the integration user limits rows. Link your own account, or set the user attribute for the integration user. | | A query fails with a database error | The Looker connection to the database failed or timed out. Check the connection under **Admin → Connections** in Looker and retry. | | Figures look out of date | The query reads from a persistent derived table or a datagroup cache. Check the datagroup trigger in LookML. | | Financial figures are missing from answers | The member's team is not in the **Financial models** data area. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [Tableau](https://hebno.com/docs/integrations/tableau.md) * [Google BigQuery](https://hebno.com/docs/integrations/bigquery.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.