Databricks Driver for Tableau

You install the databricks driver for tableau to link your charts with cloud data. This software lets your reporting app send SQL queries straight to your cluster. Most teams set up this link by sharing a workspace URL and a personal token. When teams share broad tokens, any chart user can read every table in that role.

How the databricks driver for tableau works

The driver acts as a translator between your chart tool and your cloud cluster. You download the installer package from the vendor site and place it on the machine. Desktop users install the file on their laptops. Server teams install the file on the central host machine. Once installed, the reporting tool shows a built-in connector option for your warehouse.

To start a session, the user enters the server hostname and the cluster path. Next, the user picks a login method. Many teams use personal tokens, while others use single sign-on through an identity provider. The driver takes these details and opens a secure network link over HTTPS. When a user builds a chart, the app turns that action into a SQL query. The driver sends this query to the cluster and brings back the result rows.

Choosing between tokens and identity login

How you log in shapes both daily work and security. Personal tokens are simple strings that belong to one user or a shared bot account. A user copies the string from the workspace and pastes it into the chart app. These tokens often last a long time and stay saved inside workbook files. If a teammate shares a workbook, that saved token might move with the file.

Single sign-on links the chart tool to your company login system. Each person logs in with their own work email and password. The identity system passes a short token to the driver. This approach ties every query to a real person in the cluster logs. Still, shared dashboards on a central server still often fall back to one service account.

What the native setup solves and what keeps the session active

The native driver handles network traffic, data types, and result fetching very well. It turns visual clicks into fast SQL queries that run on big clusters. Combined with workspace roles, it decides who can log in and which schemas they see. If a role lacks read access to a table, the cluster blocks the query.

Yet this setup leaves a gap during active sessions. Workspace roles check who logs in, not what each query does in flight. Once a role grants access to a table, the driver pulls every column and row by default. If that table holds customer emails, phone numbers, or card numbers, those values flow through. A shared server account makes this harder to track. Every chart query looks like it came from the same bot user in the logs. Teams must also rotate static tokens across dozens of saved reports by hand.

Add runtime guardrails and masking beside your databases and APIs

Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits beside the service as an open-source proxy, a sidecar for your database or API.

Before a query runs, hoop.dev guardrails check the statement against your rules. An AI Analyzer you configure can score intent or hold risky calls for human review. Next, hoop.dev data masking rewrites sensitive fields in responses, and each verdict is logged per listener. Explore the MIT-licensed project on GitHub.

Frequently asked questions

Where do I install the driver for shared dashboards?

You must install the driver on every node that runs your central reporting server. Desktop authors also need the local driver on their machines to build and publish charts.

Why do all dashboard queries show the same user in cluster logs?

Published reports often use one shared service account to refresh data on a schedule. Because the server uses one token, the cluster logs every query under that single account.

How can I protect sensitive columns when users build charts?

Native roles block whole tables, or you must maintain separate views with hidden columns. Data masking rewrites matched fields like emails or card numbers in results before charts load.

Related guides

• Jwt Id Token
• Jwt Token Encryption Algorithm
• Jwt Token Iat