> 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/freelucy/work-in-the-app/delete-relationship.md).
# Delete a relationship
Remove a relationship from your primary element.
Removing a relationship stages it for deletion. Like every other edit, it is not removed from ServiceNow until you commit.
{% hint style="warning" %}
**Deletion must be enabled.** If your administrator has not authorized YouDesign Freelucy to delete relationships, the remove action has no effect on commit. See [Enable relationship deletion](/freelucy/configuration/enable-relationship-deletion.md).
{% endhint %}
## In Flow
1. Find the relationship row in the upstream or downstream column.
2. Use the **remove** action button on the row.
The row is marked for removal with a strikethrough. It stays visible so you can change your mind, with an **Undo** action right there on the row.
## In Classic
1. Grab the connection point next to the element you want to remove.
2. Drag it away from the primary element and release.
3. Confirm the removal if you are prompted.
The relationship is staged for deletion. It is not removed from ServiceNow until you [commit](/freelucy/work-in-the-app/commit-changes.md). Until then you can undo the removal and keep the relationship.
***
## What's next
* [Commit your changes](/freelucy/work-in-the-app/commit-changes.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/freelucy/work-in-the-app/delete-relationship.md?ask=&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.
