# Gatekeeper

![Gatekeeper Ltd - Member | SecurityScorecard Partner Portal Partner Directory](https://assets.relyanceuat.xyz/images/docs/34386034863373/ext-d0bbba8055.png)
**Gatekeeper** is a cloud-based contract and vendor management platform that helps businesses track, store, and automate contract workflows.

To connect Gatekeeper to Relyance AI you will need an API Key.

#### In Gatekeeper

1. Login to your Gatekeeper account and refer to **Settings**> **Configuration** on the left side bar. Then select **Integration** from the menu.
2. Copy the **API Key**

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34386034863373/34386034861837.png)

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34386034863373/34386072854285.png)

#### In the Relyance AI application

1. Login to your Relyance AI account.
2. Navigate to the **Settings Menu** in the bottom left-hand side.
3. Select **Integrations**.
4. Search for **Gatekeeper** and click it to open its connections.
5. Select **Custom** under **Authentication Method**. Select all applicable features. To read more about each integration feature, you may access this article: [Integration Features](/docs/introduction-to-relyance-ai/integration-features/).

    The **Authentication** step asks for:

    - **API Token**: required; held as a secret.
6. Insert the **API Key** into the respective field and hit **Connect.**

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34386034863373/34386329412365.png)

7. Congratulations! You are now connected to **Gatekeeper.**

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A feature you enabled returns nothing.** Some scopes belong to a feature rather than to the connection: **Data subject requests** needs `Read Users`. Turning the feature on after the connection exists does not widen the grant it already holds, so re-authenticate the connection.
2. **A credential rotated at the vendor is not picked up here.** **API Token** is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

<!-- failure-modes:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "gatekeeper" {
  vendor = "gatekeeper"
  name   = "<your connection name>"

  auth = {
    method = "api-token"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      api_token = var.gatekeeper_api_token
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->