# Databricks: Managing Access to Groups

In this tutorial, you'll learn how to configure [Key Concepts](/how-abbey-works/concepts.md#grant-kits) to automate access requests to a [Databricks Group](https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/group) by attaching [Group Members](https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/group_member). This use case models Role-Based Access Control (RBAC) for Databricks.

We will be using the [Databricks Starter Kit](https://github.com/abbeylabs/abbey-starter-kit-databricks) as a base and replace configuration stubs for our use case.

## Before you start

1. **Make sure you have:**
   * An [Abbey account](https://app.abbey.so/sign-up)
   * An [Abbey API Token](/admin/managing-api-tokens.md#creating-new-api-tokens)
   * A Databricks account
2. **Make sure you setup:**
   1. A [Databricks Starter Kit](https://github.com/abbeylabs/abbey-starter-kit-databricks) by following [Get a Starter Kit](/build-a-grant-kit/get-a-starter-kit.md)
   2. A Connection to a repo by following [Connect a Repo](/build-a-grant-kit/connect-a-repo.md)

## Step 1: Configure Your Grant Kit

### Configure Output

Grant Kits rely on your GitHub account and repository name to output access changes, which we'll set through Terraform local variables. Update the `locals` block in `main.tf` with your `account_name` and `repo_name`

{% code title="main.tf" %}

```hcl
 locals {
  account_name = "" #CHANGEME
  repo_name = "" #CHANGEME
  ...
}
```

{% endcode %}

### Configure Reviewers

Workflow defines who should approve an access request. 

Let's update the `reviewers` block by adding yourself as the reviewer by switching `replace-me@example.com` with the email address you use to sign into Abbey. 

{% code title="main.tf" %}

```diff
 resource "abbey_grant_kit" "..." {
   ...
   workflow = {
     steps = [
       {
         reviewers = {
-          one_of = ["replace-me@example.com"] # CHANGEME
+          one_of = ["alice@example.com"]
```

{% endcode %}

## Step 3: Link Databricks with Abbey

Now you'll need to link [Databricks with Abbey](https://developers.abbey.io/#operation/createAppData). 

{% code title="" %}

```diff
curl -X POST \
  -H "Authorization: Bearer $ABBEY_API_TOKEN" \
  -H 'Content-Type: application/json' \
  https://api.abbey.io/v1/users/<user_id>/apps \
  -d '{"type": "databricks", "data": {"user_name": "<your Databricks user name", "tf_resource_id": "<the id of the Terraform resource for your user>"}}'
```

{% endcode %}

## Step 3: Replace Databricks-Related Stubs

You'll need to log into your Databricks account to get your database, role, user(s), table schema, and table name.

{% code title="main.tf" lineNumbers="true" %}

```diff
...

resource "databricks_group" "pii_group" {
  display_name               = "PII Group"
  allow_cluster_create       = true
  allow_instance_pool_create = true
}

- resource "databricks_user" "replace_me_user" {
+ resource "databricks_user" "alice_user" {
-  user_name    = "replace-me@example.com"
+  user_name    = "alice@example.com"
}

...
```

{% endcode %}

## Step 4: Deploy Your Starter Kit

First, add your Databricks-related secrets to your repo:

* `DATABRICKS_HOST`
* `DATABRICKS_TOKEN`

You can find this information in your Databricks account.

<details>

<summary>What should it look like?</summary>

<img src="/files/4KX2u7weKZgrxz3kVQO3" alt="" data-size="original">

</details>

To deploy your Starter Kit, follow instructions from [Deploy Your Grant Kit](/build-a-grant-kit/deploying-your-grant-kit.md).

## Step 5: Automate Access Management

:tada: Congratulations! Abbey is now managing permissions to your Databricks Group for you. :tada:

You can now start requesting and approving access by following the [Request Access](/build-a-grant-kit/requesting-access.md) and [Approve or Deny Access Requests](/build-a-grant-kit/approving-or-denying-access-requests.md) guides.

{% hint style="success" %}
Abbey strives to help you automate and secure access management without being intrusive.

To that end, this Pull Request contains native Terraform HCL code using normal open source Terraform Provider libraries. It represents the permissions change. In this case, it's just a simple creation of a new Terraform Resource.
{% endhint %}

## Next Steps

To learn more about what [Resources](/resources/privacy-policy.md) you can configure, try one of our [Tutorials](/getting-started/tutorials.md).&#x20;

For more information on how Abbey works, visit the [Key Concepts](/how-abbey-works/concepts.md) or [Grant Kits](/reference/grant-kits.md) page.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.abbey.io/getting-started/tutorials/databricks-managing-access-to-groups.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.