> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clarityq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting Your Data Warehouse Account

> Some connections run every query under your own data warehouse identity. Connect your account once so your warehouse applies your permissions to what you ask.

Most connections run queries as a service account, and ClarityQ's own permissions decide what you can reach. Some are configured to run each query **as the person asking**, so your data warehouse applies your own grants, row filters and masks. On those connections you connect your warehouse account to ClarityQ once, and only you can use it.

## Do I need to connect?

You will know: on a connection that runs queries as you, a new chat shows a **Connect your Databricks account** card above the message box, and an existing chat shows a notice on the message box. Click **Connect Databricks** and you come straight back to the chat afterwards, with a confirmation naming the account you connected.

To manage your connections, open **Settings → Apps** and look at the **Data Warehouse** section at the top. Only connections that run queries as you are listed; the ones that use a service account need nothing from you and do not appear. Each card shows one of:

* **Not connected** — click **Connect** before asking questions on it.
* **Connected**, with *Signed in as* your warehouse account. **Reconnect** refreshes the sign-in; **Disconnect** removes it.
* **Connected**, with a warning that your sign-in expires in a few days. **Reconnect** to keep access.
* **Sign-in expired** — your sign-in lapsed or was revoked in the warehouse. **Reconnect** to see data again.

Two days before your sign-in lapses, a banner at the top of ClarityQ reminds you to reconnect; you can dismiss it once per sign-in. If it lapses in the middle of a conversation, the message box says your sign-in has expired and offers **Reconnect**, and dashboards show a connect prompt in place of their widgets. ClarityQ never runs your question as the service account instead.

## Connecting

<Steps>
  <Step title="Click Connect">
    From the card in Ask Anything, the notice on the message box, a dashboard that asks you to connect, or from **Settings → Apps → Data Warehouse**. You are sent to your data warehouse's sign-in page. Sign in with **your own** account, the one that matches your ClarityQ email. ClarityQ refuses a sign-in from a different account.
  </Step>

  <Step title="Allow ClarityQ to run SQL for you">
    Approve the consent screen. ClarityQ asks only for the ability to run SQL and to stay signed in; it cannot change data or settings in your warehouse.
  </Step>

  <Step title="Ask away">
    You land back in ClarityQ with the connection marked **Connected**. Your questions, dashboards and scheduled tasks on this connection now run as you.
  </Step>
</Steps>

## What runs as you

* **Questions in Ask Anything**, including retries and corrections.
* **Dashboards**: every viewer sees the rows their own account is allowed to see, even on a dashboard someone else built.
* **Scheduled tasks you own**: they keep running as you while your sign-in is valid. If it expires, the task fails until you reconnect; your workspace admin can lengthen the sign-in on the warehouse side.

Catalog discovery and sample values are shared for the whole workspace and are collected by the service account.

## Embedded ClarityQ

Signing in to your warehouse needs a full-page redirect, which cannot run inside an embedded view. A workspace whose connection runs queries as the asking user is therefore not available when ClarityQ is embedded in another application. Ask your workspace admin if you need it there.

## Disconnecting

**Disconnect** removes ClarityQ's access to your account for that connection, and clears the results ClarityQ had cached for you on it, so dashboards stop showing rows you fetched earlier. Until you connect again, questions on it are refused. Your warehouse admin can also revoke ClarityQ from the warehouse side, which shows up here as **Reconnect required**.
