Skip to main content
The first step to using ClarityQ is connecting your data warehouse. ClarityQ uses read-only access to query your data — it never writes to or modifies your database.

Supported Data Warehouses

BigQuery

Google BigQuery

Snowflake

Snowflake

Redshift

Amazon Redshift

PostgreSQL

PostgreSQL

Databricks

Databricks

MaxCompute

Alibaba Cloud MaxCompute

Athena

Amazon Athena

Trino

Trino (incl. Starburst)

ClickHouse

ClickHouse

Azure SQL

Azure SQL Database and Managed Instance

Setup Process

You need permission to manage the data warehouse connection, which Admins, Analyst Contributors, and Integration Managers have.
  1. Configure credentials — Follow the platform-specific guide to create a service account or user with read-only access.
  2. Start the wizard — It opens on a welcome screen; click Start.
  3. Select your data warehouse — Choose from the supported platforms above.
  4. Enter your connection details, then click Test Connection. The Finish button stays disabled until the test passes, so you can’t save a connection that doesn’t work.
The setup wizard walks you through each step. Most connections take under 10 minutes to configure.

What Happens After You Connect

Connecting a warehouse doesn’t give ClarityQ your tables — you choose them. The wizard’s final screen offers Add tables now, which opens the Add Tables to the Context wizard in the Table Catalog. That wizard runs in four steps: select the tables, add table documentation, define mandatory filters, and review what you added. See Setting Up Your Table Catalog for the full walkthrough.

What Every Connection Includes

  • Read-only access — ClarityQ never writes to your database
  • Encrypted data transmission via SSL/TLS
  • Authentication options tailored to each platform (service accounts, IAM roles, dedicated users)
  • Connection pooling for optimal performance
  • Troubleshooting steps in each platform guide

Per-User Permissions

By default every query runs as the service account you configure, and ClarityQ’s roles decide what people can reach. If your data warehouse already enforces who may see which rows, Databricks and Trino connections can instead run each query under the asking user’s own identity, so your warehouse’s grants, row filters and masks apply to what they ask. Each person then connects their own account once.