> ## Documentation Index
> Fetch the complete documentation index at: https://docs.accessowl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Databricks

AccessOwl integrates with Databricks to provision and deprovision user access in your Databricks account. AccessOwl supports account level user management for Databricks.

## Capabilities

<CardGroup cols={2}>
  <Card title="Provisioning" icon="user-plus">
    AccessOwl creates user accounts with the specified roles and permissions during access requests.
  </Card>

  <Card title="Deprovisioning" icon="user-minus">
    AccessOwl deletes users from your Databricks account during access revocations.
  </Card>
</CardGroup>

## Prerequisites

* **Account admin** access in Databricks, so you can invite the integration account.

## Setup

<Steps>
  <Step title="Add Databricks in AccessOwl">
    Either add a new application or open Applications and click the +-symbol, then continue.
  </Step>

  <Step title="Invite the integration account as Account Admin">
    AccessOwl shows you the integration account's email address. In Databricks:

    * Log in to the [account console](https://accounts.cloud.databricks.com).
    * In the sidebar, click **User management**.
    * On the **Users** tab, click **Add user**.
    * Enter the integration account's email address and click **Add user**.
    * Grant the integration account the **Account admin** role.

    <Note>
      The integration account requires the Account admin role so it can add and delete users across all workspaces in your Databricks account.
    </Note>
  </Step>

  <Step title="Ensure account admins have access to the Permissions tab">
    For AccessOwl to support automated deprovisioning, ensure that account admins have access to the **Permissions** tab. You can find it under **Account** -> **Workspaces** (open your workspace) -> **Permissions**.

    <Note>
      In some cases you might need to enable identity federation by attaching a Unity Catalog metastore first.
    </Note>
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="What is the difference between deactivating and deleting a user in Databricks?">
    Databricks supports both deactivation and deletion. Deactivation prevents a user from authenticating but preserves their permissions and objects, so they can be restored later. Deletion is permanent and causes jobs owned by the user to fail, clusters to stop, and shared queries or dashboards to lose their owner. AccessOwl uses deletion during deprovisioning, so assets owned by the user should be reassigned before revoking access if continuity matters.
  </Accordion>
</AccordionGroup>