# Trino consumers

A **Trino consumer** generates a ready-to-use Trino connection string in a few clicks. Previously, connecting an external tool to your project over Trino meant creating a service account, generating API keys, and assembling the connection string by hand. A Trino consumer does all of that for you.

You'll find them in the Connectors service, under the **Consumers** tab — in the **Trino consumers** section of **Registered consumers**.

![trino-consumers](picts/trino-consumers-section.png)

?> Unlike the PowerBI and OpenLineage consumers (which you connect once), you can create as many Trino consumers as you need — each with its own name, permission level, and credentials.

- [Create a Trino consumer](#create-a-trino-consumer)
- [Manage the linked service account](#manage-the-linked-service-account)
- [Use the connection string](#use-the-connection-string)
- [Query a different catalog](#query-a-different-catalog)

---

## Create a Trino consumer

1. In the **Trino consumers** section, click **+ New Trino consumer**.

   ![trino-consumer-new](picts/trino-consumer-new.png)

2. Give it a **name**, an optional **description**, and optional **tags**.

3. Set the **permission** — the access level this Trino consumer has on your data:

   | Permission | Access |
   | :--- | :--- |
   | **READ** | Query and retrieve data only. |
   | **READ & WRITE** | Query, retrieve, and modify data. |

   ![trino-consumer-permission](picts/trino-consumer-permission.png)

4. Click **Create**.

5. Your **Trino connection string** appears.

   ![trino-consumer-connection-string](picts/trino-consumer-connection-string.png)

!> Copy the connection string now and store it somewhere safe (for example, a password manager). You can't view it again after you close this window — if you lose it, you'll have to create a new Trino consumer.

---

## Manage the linked service account

Each Trino consumer has a dedicated [service account](/en/product/iam/users/service-accounts.md) in your project's Identity Access Manager. After you create the consumer, click **Go to service account settings** to view and manage it.

The project **admin also receives an email** containing the Trino connector credentials.

---

## Use the connection string

The connection string is ready to paste into any external Trino-compatible client or BI tool. It embeds the credentials and follows this shape:

```url
trino://<api-key>:<secret-key>@<project>-query.eu.dataplatform.ovh.net:443/<catalog>
```

Plug it into your tool of choice — for example:

{Deploy Apache Superset}(/#/en/getting-further/install-apache-superset/index)

{Connect Metabase to Data Platform via Trino}(/#/en/getting-further/metabase-trino-connector/index)

!> Any user connecting through a Trino consumer accesses data according to the consumer's permission and the project's [IAM roles and groups](/en/product/iam/users/index.md). Treat the connection string like a password.

---

## Query a different catalog

By default, the connection string targets your project's **default dataset** catalog (the trailing `/<catalog>` segment, e.g. `db_<project>_default_dataset`).

To query a **different catalog** in the project, replace that trailing `/<catalog>` segment of the connection string. To list the available catalog names, run the following in the [Lakehouse Manager Explorer](/en/product/lakehouse-manager/explorer/index.md):

```sql
SHOW CATALOGS
```

For the full breakdown of the connection string and how to build one by hand, see [Integrating Trino with External Tools](/en/getting-further/integrate-trino-with-external-tools/index.md).

?> Writing data through Trino sometimes requires an explicit `CAST`. See [Trino data types and casts](/en/getting-further/trino-types-and-casts/index.md) for the mapping between Lakehouse types and Trino types, and for troubleshooting `TYPE_MISMATCH` errors.

---

### Need help? 🆘

> At any step, you can create a ticket to raise an incident or if you need support at the [OVHcloud Help Centre](https://help.ovhcloud.com/csm/fr-home?id=csm_index). Additionally, you can ask for support by reaching out to us on the Data Platform Channel within the [Discord Server](https://discord.com/channels/850031577277792286/1163465539981672559). There is a step-by-step guide in the [support](/en/support/index.md) section.