# Postgres: Managing Access to Roles

In this tutorial, you'll learn how to configure [#grant-kits](https://docs.abbey.io/how-abbey-works/concepts#grant-kits "mention") to automate access requests to a [Postgres Role](https://registry.terraform.io/providers/cyrilgdn/postgresql/latest/docs/resources/postgresql_grant_role). This use case models Role-Based Access Control (RBAC) using core Postgres components.

We will be using the [Postgres Starter Kit](https://github.com/abbeylabs/abbey-starter-kit-postgres) 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](https://docs.abbey.io/admin/managing-api-tokens#creating-new-api-tokens)
2. **Make sure you setup:**
   1. A [Postgres Starter Kit](https://github.com/abbeylabs/abbey-starter-kit-postgres) by following [get-a-starter-kit](https://docs.abbey.io/build-a-grant-kit/get-a-starter-kit "mention")
   2. A Connection to a repo by following [connect-a-repo](https://docs.abbey.io/build-a-grant-kit/connect-a-repo "mention")

## 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 2: Link Postgres with Abbey

Now you'll need to link [Postgres 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": "postgres", "data": {"role": "<your Postgres role>"}}'
```

{% endcode %}

## Step 3: Deploy Your Starter Kit

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

* `PG_PASSWORD`

<details>

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

<img src="https://1502779850-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FudoTqG501gLo2MLzBG55%2Fuploads%2FA1ZIXlGM2cVguv1ZQk7W%2Fpg-config.png?alt=media&#x26;token=dcebdb5c-40e1-4a3e-8e89-56cb8d15ce64" alt="" data-size="original">

</details>

You can optionally set the following variables as secrets or just provide a default.

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

```hcl
variable "pg_host" {
  type = string
  default = "postgres_server_ip" # CHANGEME
  sensitive = true
}
variable "pg_port" {
  type = number
  default = 5432
  sensitive = true
}
variable "pg_db" {
  type = string
  default = "postgres" # CHANGEME
  sensitive = true
}
variable "pg_username" {
  type = string
  default = "postgres_user" # CHANGEME
  sensitive = true
}
variable "pg_password" {
  type = string
  default = "postgres_password" # CHANGEME
  sensitive = true
}

variable "pg_connect_timeout" {
  type = number
  default = 15
}
```

{% endcode %}

To deploy your Starter Kit, follow instructions from [deploying-your-grant-kit](https://docs.abbey.io/build-a-grant-kit/deploying-your-grant-kit "mention").

## Step 4: Automate Access Management

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

You can now start requesting and approving access by following the [requesting-access](https://docs.abbey.io/build-a-grant-kit/requesting-access "mention") and [approving-or-denying-access-requests](https://docs.abbey.io/build-a-grant-kit/approving-or-denying-access-requests "mention") 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](https://docs.abbey.io/resources "mention") you can configure, try one of our [](https://docs.abbey.io/getting-started/tutorials "mention").

For more information on how Abbey works, visit the [concepts](https://docs.abbey.io/how-abbey-works/concepts "mention") or [grant-kits](https://docs.abbey.io/reference/grant-kits "mention") page.