> 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/getting-started/part-2-intermediate/single-relations.md).

# Single relations

**Single relations** help you fetch data from the **related collections**. 

To illustrate how it works, let's imagine we have the `Transactions` table that doesn't contain a **customer's email** and the `Users` table that contains the customer information including the email:

![](/files/-MkNPkf61ukzo95Sex7S)

And we want to **display the email** in the `Transactions` list:

![](/files/-MkNSOI-p4c83n5VXJT5)

First of all, we identify how our tables are **related**: for each user, there are several transactions that are related to the users list by the **ID** and **Customer ID fields:**

![](/files/-MkNN1Zfv7MgU1uT4A6a)

Now, let's create a new **custom column** in the `Transactions` table:

![](/files/-MkNTfKtz24SDPcnPcsU)

Then change the **column type** to `Link to record`

![](/files/-MkNUgvW4-UXL5u_HPQL)

Now, we need to select where we'll get the user email from (a related `Users` table), what field in the `Users` table is used to set relations with the `Transactions` table (the `ID` field), and what field from the `Users` table we'd like to display (the `Email` field):

![](/files/-MkNWT6xG9xGbSQ0OZDQ)

And the **final step** is to get our custom field value from the `Transactions` table field that sets relations to the `Users` table (the `Customer ID` field):

![](/files/-MkNXnKZh7yXZuEOwA7k)

Now, let's make UI components **dynamically visible** based on a rule:

{% content-ref url="/pages/-Mkg6VpZJSj1ZRY0u6Qf" %}
[Conditional Visibility](/getting-started/part-2-intermediate/conditional-visibility.md)
{% endcontent-ref %}


---

# 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.jetadmin.io/getting-started/part-2-intermediate/single-relations.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.