Skip to main content

Looker and the Catalog Browser Extension

While you view dashboards in Looker, the Catalog browser extension connects what you see in the browser to metadata synced in Catalog. This guide describes what you need in place, how different Looker dashboard URL patterns relate to Catalog, how to confirm the extension picked the right dashboard, and what to try when something looks off.

Before You Begin​

You need the following before the extension can show useful Catalog metadata for a Looker dashboard:

  • Looker content in Catalog - Dashboards and related Looker assets must be synced through the Looker integration. If extraction has not completed or a dashboard was added recently, wait for the next sync or run your extraction process according to your setup.
  • Access to Catalog - Sign in to your Catalog Workspace in the browser where you use the extension so the extension can load metadata you are allowed to see.
  • A supported browser - Install the extension in Chrome or Edge. Edge users install from the Chrome Web Store with extensions from other stores allowed. Full browser notes are on the Browser Extensions page.
Looker Admin Versus Extension Use

Configuring the Looker integration requires Looker admin credentials and API access. Day-to-day extension use only requires that your organization finished syncing Looker to Catalog and that you can sign in to Catalog.

Install the Catalog Browser Extension​

If you have not installed the extension yet, follow How to Install the Extension on the Browser Extensions page. Your organization can also push the extension using the extension ID on the Company-Wide Install page.

How Looker Dashboard URLs Relate to Catalog​

Looker dashboard addresses vary by instance. You might see a numeric dashboard ID in the path, a readable slug, or another URL shape your Looker admin configured. Catalog is built to recognize the dashboard you have open from these URL patterns so the extension can load the matching Catalog asset.

Use this flow when you verify behavior:

  • When the URL includes a numeric dashboard identifier, Catalog associates the open page with the corresponding dashboard metadata ingested from Looker.
  • When the URL uses a slug or another stable identifier in place of a bare numeric segment, Catalog still resolves the open dashboard to the same Catalog asset when extraction captured that dashboard.

If your instance switches URL styles between environments or after publishes, wait until Catalog finishes ingesting the revision you care about, then refresh the Looker page and open the extension again.

Confirm the Extension Shows the Right Dashboard​

Work through these checks when you first use the extension or after large Looker changes:

  1. Open a Looker dashboard that you know exists in Catalog. If you are unsure, search for it in Catalog first.
  2. Activate the Catalog extension from the browser toolbar. The extension panel opens beside your Looker content.
  3. Confirm metadata matches what you expect for that dashboard, including descriptions, ownership, and popularity fields shown for your Workspace.
  4. If your Workspace licenses Dashboard Q&A, open that capability from the extension and ask a simple factual question about the dashboard to confirm context lines up with the asset you selected in Catalog.

If labels or owners differ between Looker and Catalog, resolve extraction or synchronization first; the extension reflects what Catalog stores after integration runs.

Troubleshooting​

These situations cover the most common extension issues in Looker workflows.

The Extension Does Not Appear or Stay Pinned​

Confirm the extension is installed and enabled for your browser profile. On Edge, confirm you allowed extensions from the Chrome Web Store. Reload the Looker tab after enabling the extension. If your organization manages extensions centrally, ask your IT administrator to confirm the Catalog extension is allowed using the ID on Company-Wide Install.

Metadata Describes a Different Dashboard or Looks Empty​

Check that you are signed in to Catalog in the same browser and that the dashboard URL matches what was extracted, whether the path uses a slug or a numeric dashboard identifier. Run through How Looker Dashboard URLs Relate to Catalog, then refresh the Looker page and open the extension again after extraction completes.

Sign-In or Permission Errors in the Extension​

Clear stale Catalog sessions by signing out and back into Catalog in the browser, then reload Looker. If your organization uses more than one Catalog region or tenant, confirm you are logging into the Workspace that matches your Looker integration. When errors persist after those checks, capture the browser message you see and contact Catalog Support with your Workspace name and the Looker dashboard URL you had open.

Catalog Web App Versus the Browser Extension

Problems that appear only inside the Catalog web application are separate from the Chrome or Edge extension. Note whether an issue reproduces on app.castordoc.com alone or only when the extension panel is open so support can route the report quickly.

What's Next?​