# Ironclad

![download__4_.png](https://assets.relyanceuat.xyz/images/docs/35136854056845/35136854037517.png)
Ironclad is a contract lifecycle management platform used by companies to handle different types of contract management workflows.

The Ironclad integration will allow you to connect agreements in Ironclad with Relyance.

In order to connect to Ironclad, you'll need an Client ID

, Client Secret

, and/or Template ID's

, and/or Record Types

, and to follow an OAuth2 workflow.

Ironclad's API doesn't provide a way to specify folders during the integration process. Relyance will download all documents from Ironclad. It is possible to specify which

Template ID or Record type to download contracts from.

### Which method to choose

All three use the same credentials — **API Server**, **Client ID** and **Client
Secret** — and differ only in what they pull:

| Method | Retrieves |
| --- | --- |
| **All Workflows** | every workflow and its documents |
| **Specify Template** | only the templates you name (comma-delimited) |
| **Retrieve All Records** | records rather than workflows; name record types, or leave empty for all |

The authorisation grants `public.workflows.readWorkflows`,
`public.workflows.readDocuments`, `public.records.readRecords`,
`public.records.readSchemas` and `public.records.readAttachments` — all read-only.

Start with **Specify Template** if only some contract types are in scope: it is
the difference between scanning a handful of templates and every workflow in the
instance.

#### In Ironclad:

- Follow the instructions found here to create a **Client ID** and **Client Secret**: [https://developer.ironcladapp.com/reference/register-oauth-client](https://developer.ironcladapp.com/reference/register-oauth-client) For the redirect URI use: [**https://root.relyance.ai/api/oauth2**](https://root.relyance.ai/api/oauth2)

Please ensure you have the following permissions for the OAuth2 client:

- public.records.readAttachments
    - public.records.readRecords
    - public.records.readSchemas
    - public.workflows.readDocuments
    - public.workflows.readWorkflows
- ( *optional* ) If limiting documents to a specific workflow, grab the **Template ID** in question by navigating to Ironclad's dashboard and selecting All Workflows from the left-hand navigation menu. Select your workflow in question This will open up the workflow info. Copy the Template ID found at the end of the URL on the following page.
- (optional) You can also limit documents to a specific record type.

![IronClad-2.png](https://assets.relyanceuat.xyz/images/docs/35136854056845/35136838255245.png)

#### In Relyance:

1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **Ironclad** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    - **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    - **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    - **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, provide the following information retrieved from the **In Ironclad** section and click on **Continue**.
    - **API Server** **EU Region:** `eu1.ironcladapp.com`**US Region:** `na1.ironcladapp.com` Note: Choose the API Server based on the region where your Ironclad server is hosted.
    - **Client ID**
    - **Client Secret**, and/or
    - **Template ID's**, and/or
    - **Record Types**
10. Review the configuration summary from the **Completion** section and click on **Finish.**
11. Confirm the integration Status reflects **Connected**

![Ironclad_overview_20250224_195917.png](https://assets.relyanceuat.xyz/images/docs/35136854056845/35136854040973.png)

![Ironclad_overivew2.png](https://assets.relyanceuat.xyz/images/docs/35136854056845/35136838260621.png)

![Ironclad_connection_20250224_195928.png](https://assets.relyanceuat.xyz/images/docs/35136854056845/35136838260749.png)

![Screenshot 2025-11-05 185700.png](https://assets.relyanceuat.xyz/images/docs/35136854056845/40889117698445.png)

![Ironclad_completion_20250224_195932.png](https://assets.relyanceuat.xyz/images/docs/35136854056845/35136838263309.png)

<!-- 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`.

### OAuth (browser authorization) — All Workflows

The **OAuth (browser authorization) — All Workflows** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example ironclad/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

### OAuth (browser authorization) — Specify Template

The **OAuth (browser authorization) — Specify Template** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example ironclad/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

### OAuth (browser authorization) — Retrieve All Records

The **OAuth (browser authorization) — Retrieve All Records** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example ironclad/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

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