Databricks
Databricks integration
Data PlatformAvailable
BRAIAN connects to Databricks through SQL Warehouse endpoint, service principal. Agents can sql warehouse queries, unity catalog lineage read and table access under catalog permissions. Every action is scoped by the permissions granted to the integration and executed under a versioned policy. Each one is recorded in the audit log with the agent, timestamp and record touched.
What can BRAIAN do?
Agents query the SQL warehouse for the figures a process needs and read lineage from Unity Catalog. Table access is decided by Unity Catalog grants, which are enforced natively rather than reimplemented.
| Capability | Agent | Read or write |
|---|---|---|
| SQL warehouse queries | All agents | Read |
| Unity Catalog lineage read | All agents | Read |
| Table access under catalog permissions | All agents | Read |
How does it connect?
- Connection method
- SQL Warehouse endpoint, service principal
- Credential
- A Databricks service principal with an OAuth token, scoped to one workspace.
Credentials are held in an encrypted secrets store. BRAIAN never stores end-user passwords.
Which permissions are required?
- Unity Catalog grantsCatalog, schema and table grants are enforced by Databricks itself; BRAIAN adds no parallel access path.
Permissions are requested at the minimum scope the configured processes require. Unused scopes are not granted.
Which processes use it?
Processes that run on this connection, and the domains they belong to.
Invoice reconciliation
Expense audit
Data access review
Used across every business domain.
How do you revoke access?
Access is revoked in Databricks itself — by disabling the credential or removing the granted scopes — or in BRAIAN by disconnecting the integration. Processes already running stop at their next call to Databricks and are held for review rather than completed with partial data; the interruption and the state of each process are recorded in the audit log.
FAQ
Does BRAIAN store data from Databricks?
BRAIAN reads what a process needs, when it needs it. Records retrieved from Databricks are held only for the duration of the process and in the audit trail of the actions taken; Databricks remains the system of record.
What happens if the connection fails mid-process?
The process stops at the failed step and is held for review. Nothing is written twice: completed writes stay recorded in the audit log and the remaining steps resume only once the connection is restored.
Can permissions be scoped per agent?
Yes. Scopes are defined per agent, not per system, so one agent can read while another cannot, on the same connection to Databricks.
