> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/data/relationships.md).

# Relationships

Connect related records using identifiers shared between tables.

For example, each order contains a customer ID that matches a record in Customers. Several orders can refer to the same customer.

```mermaid
erDiagram
    CUSTOMERS ||--o{ ORDERS : places
    CUSTOMERS {
        number id PK
        text name
    }
    ORDERS {
        number id PK
        number customer_id FK
        number total
    }
```

* [Link related records](/user-guide/data/relationships/link-records-across-tables.md): configure a related field.
* [Many-to-many relationship](/user-guide/data/relationships/many-to-many-relationships.md): work with records related in both directions.
* [Relations View](/user-guide/data/relationships/relations-view.md): inspect related data.
* [Lookup fields](/user-guide/data/computed-fields/lookup-column.md) and [rollup fields](/user-guide/data/computed-fields/rollup-column.md): use values from related records.

Use stable IDs for matching. Display names help readers recognize a record but may not be unique. To filter one component based on another component's selected row, follow [Filter related records in Classic App Builder](/user-guide/data/relationships/filter-related-records-in-classic-app-builder.md). Practice with [Customers and Orders sample data](/user-guide/data/customers-and-orders-sample-data.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/user-guide/data/relationships.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.