> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/designer/work-in-the-app/using-relationship-fields.md).

# Using Relationship Fields

Information on how to use relationship fields

Designer supports the visualization of maximum three fields on relationships per suggested relationship.

{% hint style="danger" %}
**Adding Fields to Relationships**

Adding fields to Relationships can be performed by a ServiceNow admin only on the *cmdb\_rel\_ci* table and impacts the entire platform.

Once those fields have been added, they can be selected as Relationship Fields in Designer.
{% endhint %}

![](https://2424003387-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRt6kkrmmoQeRFJQUp63x%2Fuploads%2Fgit-blob-1346b272715c0cfdab1118ddaee04834a6c201f4%2Ff570010-designer_relationship_fields.png?alt=media)

Relationship Fields

**A** – Click Relationship Fields in the INSERT tab to see the Relationship form.

**B** – Select a relationship type.

**C** – Select the first field on the relationship defined on the cmdb\_rel\_ci table.

**D** – Select the second field on the relationship defined on the cmdb\_rel\_ci table.

**E** – Select the third field on the relationship defined on the cmdb\_rel\_ci table.

**F** – Click + ADD to add another Relationship Type with fields to be displayed.

**G** – Quickly switch on/off the relationship fields in the Designer canvas.

**H** – Click X to remove the line.

**I** – Click Apply to confirm the changes made.


---

# 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.ins-pi.com/designer/work-in-the-app/using-relationship-fields.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.