Before you connect
Network access — Databricks workspaces are accessible over HTTPS (port 443). No special firewall rules are typically needed for cloud-hosted workspaces. If your workspace is behind a private network or VPN, ensure Supaboard’s egress IPs can reach it. The current IP list is shown inside the connector form under Whitelist IPs. Cluster requirements — The cluster referenced by your HTTP path must be running when Supaboard connects. Terminated or auto-terminated clusters will cause connection failures. Permissions — The user whose access token you use needs:CAN ATTACH TOpermission on the clusterSELECTaccess on the target catalogs and schemas
Connection fields
Finding your connection details
Databricks Workspace
Personal access token (Token):- In your Databricks workspace, click your username in the top-right corner.
- Go to Settings → Developer.
- Under Access tokens, click Manage.
- Click Generate new token, add a comment (e.g.
supaboard), set a lifetime, and click Generate. - Copy the token — it is only shown once.
https://. It looks like:
- Go to Compute in the sidebar.
- Click on your cluster name.
- Scroll to Advanced options and click the JDBC/ODBC tab.
- Copy the HTTP path value (format:
/sql/1.0/endpoints/xxxxxxxxxxxxxxxxor/sql/protocolv1/o/...).
- Go to SQL Warehouses in the sidebar.
- Click on your warehouse.
- Go to the Connection details tab.
- Copy the HTTP path.
SQL warehouses are recommended over interactive clusters for BI tools — they are purpose-built for query workloads and auto-scale automatically.Documentation: JDBC/ODBC connection details · SQL warehouses overview
Recommended database user permissions
In Unity Catalog, grant the token owner the following privileges:data_access group membership or equivalent.

