# Looker

## Supported Capabilities

{% tabs %}
{% tab title="Supported Capabilities" %}
**General**

* **Metadata** — metadata extraction and display of asset information (tables, columns, schemas). Types collected: Schema, Virtual Table, Virtual Column, Chart, Dashboard
  {% endtab %}

{% tab title="Not Supported" %}
**General**

* Profiling
* Preview
* Data Quality
* Configurable Collection
* External Table
* View Table
* Stored Procedure
  {% endtab %}
  {% endtabs %}

Looker supports lineage mapping from the following sources:

* Upstream Connectors: mysql, singlestore, postgresql, redshift, snowflake, azure\_server, sql\_server, synapse, bigquery, databricks, oracle

## Connection Requirements

## Minimum Requirement

From our Looker account, we will need the following information:

* Looker instance URL
* Client ID
* Client secret

<figure><img src="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2Fgit-blob-5df61d6b4a3b7a6289d45daf066ff1adfe2b5b49%2Fimage.png?alt=media" alt=""><figcaption><p>Looker</p></figcaption></figure>

To ensure proper functionality of the ingestion process, it is imperative to grant the following permissions.

* access\_data
* develop
* explore
* manage\_project\_models
* manage\_project\_connections
* see\_lookml
* see\_lookml\_dashboards
* see\_looks
* see\_queries
* see\_sql

For more info on how to create permission sets. Please refer to this looker [documentation](https://cloud.google.com/looker/docs/admin-panel-users-roles#creating_permission_sets).

## Additional configuration for lineage

To build out the lineage, we will need to know the data sources that you've referenced within your Looker definitions. You can do a one-time mapping for the sources by using the Additional Configuration in the Data Sources page. Check out how below.

{% content-ref url="../transformation-tools/additional-configurations" %}
[additional-configurations](https://docs.decube.io/transformation-tools/additional-configurations)
{% endcontent-ref %}

For Looker, we match your Views in Looker to decube Tables by the **View name**. If you have customized View names, please refer to the next section below.

### Override View Mapping (Optional)

<figure><img src="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2Fgit-blob-8f3a3eb0cc3735fc9c0f272147bf99f30f5bdd78%2FSCR-20231018-qkus.png?alt=media" alt=""><figcaption><p>Mapping for Looker Lineage which is optional</p></figcaption></figure>

If you have a customized View name, it is recommended to use the View Mapping Override to add the name of the Table in decube so that our metadata scanner can build the lineage automatically to your Looker view.