> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/human-access/connections-and-integrations/integration-guides/databricks.md).

# Databricks

Set up Databricks auto-provisioning with an emailed sign in code read from your connected inbox.

### :sparkles: Auto Provisioning

| **Authentication method** | Email with a sign in code. Requires a connected inbox. See details [here](#how-email-verification-works).                                    |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Required permissions**  | `Account admin`                                                                                                                              |
| **Required metadata**     | `Workspace`, only when the Databricks account has more than one running workspace. See details [here](#when-do-i-need-to-enter-a-workspace). |
| **MFA**                   | Not applicable. Databricks signs in with an emailed code, so there is no MFA secret to enter.                                                |
| **Email verification**    | Required. See details [here](#how-email-verification-works).                                                                                 |

{% hint style="info" %}
**Revoking access removes the user from your company's Databricks account**, not only from the workspace. This covers every workspace they belong to.
{% endhint %}

{% hint style="info" %}
**Cakewalk supports Databricks accounts hosted on AWS.** These are managed at `accounts.cloud.databricks.com`.
{% endhint %}

<details>

<summary><strong>When do I need to enter a Workspace?</strong></summary>

Leave `Workspace` empty if your company's Databricks account has a single running workspace.

If it has more than one, enter the name of the workspace Cakewalk should manage, exactly as it appears in the Databricks account console under `Workspaces`. New users are added to that workspace. When the field is empty or the name does not match, the configuration is rejected.

</details>

<details>

<summary><strong>How email verification works</strong></summary>

Databricks has no password here. Signing in means entering the admin account's email address, after which Databricks sends a `Your verification code is` email. Agent Cake reads the code from your connected inbox and enters it.

Connect the inbox before you configure Databricks. Go to Settings → Account → *Auto Provisioning* and click **Connect Inbox**. Full steps are in [Email Verification](/docs/human-access/how-to-guides/auto-provisioning/how-it-works/email-verification.md).

Agent Cake signs in as the inbox account itself, so the connected inbox has to be the mailbox of a Databricks user with the `Account admin` role.

{% hint style="info" %}
The code is short lived. If it has not arrived by the time the login needs it, the run fails and you can retry the request.
{% endhint %}

</details>

#### Permission levels

Agent Cake can grant and remove these workspace entitlements:

* `Consumer access`
* `Databricks SQL access`
* `Workspace access`
* `Admin access`

#### Learn more

* [Databricks: Manage users](https://docs.databricks.com/aws/en/admin/users-groups/users)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.cakewalk.security/docs/human-access/connections-and-integrations/integration-guides/databricks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.