> 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/features/relationship-editor.md).

# Relationship Editor

See, add, change and remove one record's direct relationships, then review every change before it is saved.

The Relationship Editor shows everything one record is directly connected to, and lets you change those connections safely. Every change you make is held back until you review it and click **Commit**, so nothing reaches your ServiceNow data by accident.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-1d4306dd29a125dce29414491f39aa0a91844c68%2Fcommand-relationship-editor-flow.png?alt=media" alt="The Relationship Editor for a business application, with upstream relationships on the left, downstream on the right, one new relationship waiting to be committed."><figcaption><p>The Relationship Editor in the Flow view</p></figcaption></figure>

## What it is

The editor is centered on one record, called the *element*. It shows only the records directly related to it, on two sides:

| Side             | What it holds                                                                                          |
| ---------------- | ------------------------------------------------------------------------------------------------------ |
| **↑ Upstream**   | Records the element depends on or belongs to, such as the business capability an application supports. |
| **↓ Downstream** | Records that depend on the element, such as the servers an application runs on.                        |

To explore further than one step, use the Dependency Map instead.

Each relationship row can carry a marker:

| Marker                                          | What it means                                                                                                                                                           |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **New**, **Update**, **Moved**, **Removing**    | A change you have made but not committed yet.                                                                                                                           |
| **Failed**                                      | A change that could not be saved. Point at it to see why.                                                                                                               |
| **🗂 Overlay**                                  | A relationship that a plan in the [Future State Repository](https://docs.ins-pi.com/command/features/future-state-repository.md) adds. It is not in your live data yet. |
| **🔒** with a kind, such as **Reference field** | A connection the editor shows but cannot change, for example one made by a field on the record.                                                                         |
| **⚠ Neighbor is live**                          | A planned record on this relationship has since become a real record. Open it to reach that record.                                                                     |

The same relationship can be listed twice, once live and once as **🗂 Overlay**. This is intended: the plan and the live data are separate facts.

## When to use it

* You want to check what an application, capability or other record is connected to.
* You need to add or remove several relationships and review them together before saving.
* You are working on a plan and want to see which relationships it adds.

## How to

### Open the editor

Choose the way that suits where you are:

* **From any list of records**, such as a Table, a Roadmap or a Dependency Map: open the row's **⋮** menu and choose **Edit relationships**. The editor opens in a new tab named *relationships*.
* **From the Create menu**: click **+**, choose **Relationship Editor**, then drag one record onto it from the [Data Hub](https://docs.ins-pi.com/command/the-portal/data-hub.md). The editor takes that record's name.
* **From a Form**: scroll to the **Relationships** section, if your administrator has added it to the form. The **Relationships** tile at the top shows the counts; click **Upstream** or **Downstream** to jump to that side.
* **From a ServiceNow form**: click **Manage Relationships** to open the editor in Command, or use the relationship view embedded in the form.

If a tab for the same record is already open, Command switches to it instead of opening a second one.

To keep the editor, open **⋮** and choose **Save in My Space**. See [My Space and Sharing](https://docs.ins-pi.com/command/the-portal/my-space.md).

## Good to know

* Without the **Command Relationship Editor** role you can see relationships but not change them. A line under the toolbar says why.
* You can relate two records only when ServiceNow suggests that relationship between their classes. Your administrator manages these suggestions.
* Each side shows 50 relationships at first. Click **load more** at the bottom to see the rest.
* Records you are not allowed to read appear as **No read access**.

## Related

* [Add relationships](https://docs.ins-pi.com/command/features/relationship-editor/add-relationships.md)
* [Change, remove and commit relationships](https://docs.ins-pi.com/command/features/relationship-editor/change-and-commit.md)
* [Views, filters and details](https://docs.ins-pi.com/command/features/relationship-editor/views-and-details.md)
* [Relationship settings](https://docs.ins-pi.com/command/administration/relationship-settings.md) (for administrators)


---

# 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/features/relationship-editor.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.
