> 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/command/administration/relationship-settings.md).

# Relationship settings

Configure the Relationship Editor for your organization, from who can edit relationships to which fields a relationship carries.

{% hint style="info" %}
You need the **Command Admin** role to open **Global Settings**. Roles are assigned in ServiceNow by an instance administrator.
{% endhint %}

These settings decide who can change relationships, which relationships users are offered, and which fields a relationship shows in its details.

## Who can do what

| Role               | Lets a user                                                                                          |
| ------------------ | ---------------------------------------------------------------------------------------------------- |
| **Command Reader** | See relationships, including the relationship view embedded in ServiceNow forms.                     |
| **Command Editor** | Add, change and remove relationships, including the relationships that a plan adds (**🗂 Overlay**). |

Anyone who can read a record can see its relationships in Command.

## Which relationships are offered

Users can only relate two records when ServiceNow suggests a relationship between their classes. These suggestions are ServiceNow's suggested relationships, managed by your instance administrator. A user who needs a missing one sees *No suggested relationship exists between this record and …*.

## Open the settings

1. Click **Open menu** (☰) in the header and expand **Global Settings**. See [Global Settings](https://docs.ins-pi.com/command/administration/global-settings.md).
2. Choose **Relationships**.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-a5698985bbbf356242bf414b787445cdf54aaa36%2Fcommand-settings-relationships.png?alt=media" alt="The Relationships section of Global Settings, with the two editor toggles, the field sources and the relationship field combinations."><figcaption><p>Global Settings, Relationships</p></figcaption></figure>

## Settings

| Setting                           | Default                       | What it changes                                                                                                                        |
| --------------------------------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Block duplicate relationships** | Off                           | Skips a second relationship of the same type between the same two records when a user commits. Duplicates that already exist are kept. |
| **Offer suggested relationships** | Off                           | Shows suggested classes and types when a user adds a relationship.                                                                     |
| **Field sources**                 | The relationship's own fields | The tables whose fields a relationship can show in its details. Some tables can be shown but not edited.                               |
| **Relationship fields**           | None                          | Which fields appear for each combination of class, relationship type and class.                                                        |

## How to

### Show fields on a kind of relationship

1. Under **Add a table**, choose the table in **Choose a table…** and click **Save changes**, so its fields can be used.
2. Under **Relationship fields**, click **Add combination**.
3. Choose **From**, **Relationship** and **To**. The choices follow ServiceNow's suggested relationships.
4. Pick the **Table** and **Field** to show.
5. To show it to some people only, add groups under **Show only to these groups**. Leave it empty for everyone.
6. Click **Save changes**.

Users see the field the next time they open a relationship's details.

### Add the editor to a form

In **Global Settings > Forms**, place the **Relationships** section on a form layout. Add the **Relationships** tile too if you want the counts at the top of the form.

## Related

* [Relationship Editor](https://docs.ins-pi.com/command/features/relationship-editor.md)
* [Roles & Groups](https://docs.ins-pi.com/command/prior-v26.0/configuration/roles-groups.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.ins-pi.com/command/administration/relationship-settings.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.
