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

# Commit your changes

Every edit you make in YouDesign Freelucy, whether you add, update, or remove, is staged first. None of it touches ServiceNow until you commit. Commit is a gate: review the full list, then confirm.

<figure><img src="/files/XPtVEuCjMwg6IaIQfmRU" alt="" width="563"><figcaption><p>Review pending changes dialog</p></figcaption></figure>

## Step by step

1. The commit bar shows how many changes are staged. When you are ready, click **Commit**.
2. The **Review pending changes** dialog lists every staged change, grouped by what it does — **New**, **Update**, and **Delete**. Each row shows the record, its relationship type, and which side it sits on, with an **Undo** button to drop just that change.
3. Check the list. To drop a single change, use its **Undo**. To start over, choose **Discard all**.
4. When the list is right, choose **Commit**. The button shows the number of changes it will write, for example **Commit (7)**.

Freelucy writes the changes to ServiceNow in a single batch. The staged styling clears, and the relationships are now live.

## Discard instead

To drop everything staged without committing, **Discard**. Freelucy refetches the record from ServiceNow, so the editor returns to exactly what is stored. Discard cannot be undone.

{% hint style="info" %}
**Leaving with unsaved changes?** If you try to open a different record while edits are staged, Freelucy asks first so you do not lose work.
{% endhint %}

***

## What's next

* [Inspect, navigate, and share](/freelucy/work-in-the-app/inspect-navigate-share.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ins-pi.com/freelucy/work-in-the-app/commit-changes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.