> 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/change-and-commit.md).

# Change, remove and commit relationships

Change a relationship's type or side, remove relationships, undo changes and commit them in the Relationship Editor.

Every change you make in the Relationship Editor is held as a draft, marked on its row, and counted on the **Commit** button. Nothing is written to your data until you commit, and you can undo any change before then.

## How to

### Change a relationship's type or side

1. Open the row's **⋮** menu and choose **Change type**.
2. Pick the new type. The list is grouped by side, so picking a type under the other side also moves the record there.

You can also drag a row to the other side to move it, or within its own side to change its type. The row is marked **Update** or **Moved**.

**🗂 Overlay** relationships cannot be retyped or moved, only removed.

### Remove relationships

Pick whichever is quickest:

* Open the row's **⋮** menu and choose **Remove relationship**.
* Drag the row onto **Remove**.
* Select the row and press **Delete**.
* In the **List** view, check several rows and click **Remove** in the bar that appears.

The row is struck through until you commit. Click **Undo** on it to keep it.

### Undo changes

* **One change:** click **Undo** on a removed row, or choose **Undo this add** in a new row's **⋮** menu.
* **Everything:** click **Discard**.

### Commit your changes

1. Click **Commit**. The number on it is how many changes are waiting.
2. Read the **Review and confirm** window. It lists **Additions**, **Removals** and **Changes**.
3. Click **Commit** to save them, or **Cancel** to keep editing.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-a9b8b9b015ce68781fd97a4090d6b1179955a472%2Fcommand-relationship-editor-commit-review.png?alt=media" alt="The Review and confirm window listing two additions, one removal and one change before they are committed."><figcaption><p>Review your changes before committing</p></figcaption></figure>

If only some changes could be saved, a message says how many. The rest stay as drafts, marked **Failed** where the save was refused; point at the marker to see why.

## Good to know

* In a Form's **Relationships** section, click the Form's **Edit** first. The Form's **Save** then saves field edits and relationships together, after the same review.
* Closing the tab without committing loses your drafts.
* Your administrator can refuse a second relationship of the same type between the same two records. When that is switched on, a duplicate is skipped when you commit.

## Related

* [Add relationships](https://docs.ins-pi.com/command/features/relationship-editor/add-relationships.md)
* [Views, filters and details](https://docs.ins-pi.com/command/features/relationship-editor/views-and-details.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/features/relationship-editor/change-and-commit.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.
