> 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/relations-view.md).

# Relations View

Link tables together to display related data without switching between views

The Relations View in JetAdmin helps you understand how your data is connected. Easily link tables using foreign key fields and explore related records without switching tabs.

#### Steps

1. **Add a relation field:** Open your table (for example, *Tickets*) and click **Add Field → link to record**.
2. **Choose the related table:** In the setup, select *Users* as the table you want to connect to.
3. **Pick the linking field:** Choose the field from *Users* (like `User ID`) that uniquely identifies each record.
4. **Link records:** In your *Tickets* table, fill the new relation column with the correct *User ID*. Each ticket will now be linked to a user.
5. **View related data:** Click the linked user inside the cell to view that user’s details directly, no need to open the *Users* table separately.

{% @arcade/embed flowId="do6hXU4Yfp1dY0unnPLV" url="<https://app.arcade.software/share/do6hXU4Yfp1dY0unnPLV>" %}


---

# 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/relations-view.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.