> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/finance-and-accounting/concord/data-overview.md).

# Data Overview

Coupler.io pulls data from seven Concord entities. This page breaks down what fields are available in each and how you can use them together.

## Entities overview

| Entity               | Best used for                                                       |
| -------------------- | ------------------------------------------------------------------- |
| Agreements           | Contract status tracking, renewal monitoring, obligation management |
| Organizations        | Org-level settings and configuration                                |
| Organization members | User access audits, team structure                                  |
| User organizations   | Mapping users to their org roles                                    |
| Folders              | Understanding how contracts are structured and categorized          |
| Reports              | Pre-built analytics and contract insights from Concord              |
| Tags                 | Contract categorization and filtering                               |

## Agreements

#### Key fields

| Field           | Description                                           |
| --------------- | ----------------------------------------------------- |
| Agreement ID    | Unique identifier for each contract                   |
| Title           | Name or subject of the agreement                      |
| Status          | Current state (e.g., draft, pending, active, expired) |
| Type            | Category of agreement (e.g., NDA, MSA, SOW)           |
| Created date    | When the agreement was created                        |
| Effective date  | When the contract becomes active                      |
| Expiration date | When the contract expires                             |
| Owner           | User responsible for the agreement                    |
| Counterparty    | External party to the contract                        |
| Tags            | Labels applied to the agreement                       |
| Folder          | Folder the agreement is stored in                     |

## Organizations

#### Key fields

| Field           | Description                   |
| --------------- | ----------------------------- |
| Organization ID | Unique identifier for the org |
| Name            | Organization name             |
| Plan            | Subscription plan or tier     |
| Created date    | When the org was created      |

## Organization members

#### Key fields

| Field       | Description                           |
| ----------- | ------------------------------------- |
| Member ID   | Unique identifier for the member      |
| User ID     | Associated user account               |
| Role        | Member's role within the organization |
| Status      | Active or inactive membership         |
| Joined date | When the user joined the org          |

## User organizations

#### Key fields

| Field           | Description                               |
| --------------- | ----------------------------------------- |
| User ID         | Identifier of the user                    |
| Organization ID | Identifier of the associated organization |
| Role            | User's role in that organization          |

## Folders

#### Key fields

| Field            | Description                                     |
| ---------------- | ----------------------------------------------- |
| Folder ID        | Unique identifier for the folder                |
| Name             | Folder name                                     |
| Parent folder ID | ID of the parent folder (for nested structures) |
| Created date     | When the folder was created                     |

## Tags

#### Key fields

| Field  | Description                      |
| ------ | -------------------------------- |
| Tag ID | Unique identifier for the tag    |
| Name   | Tag label                        |
| Color  | Visual color assigned to the tag |

## Reports

#### Key fields

| Field        | Description                   |
| ------------ | ----------------------------- |
| Report ID    | Unique identifier             |
| Name         | Report title                  |
| Type         | Category of report            |
| Created date | When the report was generated |
| Data         | Report content and metrics    |

## Common field combinations

* **Agreements + Tags** — Join on tag ID to filter and group contracts by category (e.g., vendor, customer, legal)
* **Agreements + Folders** — Join on folder ID to understand how contracts are distributed across your folder hierarchy
* **Organization members + User organizations** — Join on user ID to build a full picture of who has access to what across multiple orgs
* **Agreements + Reports** — Combine raw agreement data with Concord's pre-built report summaries for richer dashboards

## Use cases by role

{% tabs %}
{% tab title="Legal & Contracts" %}

* Monitor agreement statuses across the full portfolio to catch contracts approaching expiration
* Use the Agreements entity to build a renewal calendar in Google Sheets or Looker Studio
* Tag contracts by type or counterparty, then filter in your destination to prioritize reviews
  {% endtab %}

{% tab title="Finance" %}

* Pull agreement data alongside financial records to match contract obligations with budget items
* Use Aggregate transformations to count active agreements by type or counterparty for spend analysis
* Track contract creation trends over time using the created date field in Reports
  {% endtab %}

{% tab title="Operations" %}

* Audit organization members and their roles to ensure access permissions are appropriate
* Use the Folders entity to validate that contracts are organized consistently
* Feed Agreements data into ChatGPT or Claude to generate contract summaries or flag missing terms
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Concord's API is accessed via API key — OAuth is not supported
* The Reports entity returns Concord's own pre-built report data, not raw event logs
* Nested folder structures are represented via parent folder IDs — you'll need to join the Folders entity to itself to reconstruct the hierarchy
* Tag and folder associations are stored on the Agreements entity, making it the natural center for most joins


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/finance-and-accounting/concord/data-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.