> 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/get-started/tour-the-editor.md).

# Tour the editor

The editor is where you stage relationship changes. Whatever view you are in, the same parts are always within reach: the header, the view tabs, the Data Hub, and the commit bar.

{% hint style="info" %}
The first time openning YouDesign Freelucy will show you a tutorial where you can have a overview in realtime of the app, if you want to see it again you can click on Show tutorial from the top-left icon
{% endhint %}

## The header

<figure><img src="/files/sZRrffjo5x7Cve6ssd9k" alt="" width="166"><figcaption><p>Top-left icons</p></figcaption></figure>

The header sits across the top on every page.

* **Home and branding** take you back to record selection.
* **Page name and tag** show the record you are editing.

<figure><img src="/files/ZZZoOxvf5DoIaNRHaxa3" alt="Hamburger icon shows the left panel" width="188"><figcaption><p>Top-left hamburger icon shows the left panel</p></figcaption></figure>

* **Theme toggle** switches between light and dark. See [Themes and language](/freelucy/personalize-and-accessibility/themes-and-language.md).
* **Language switcher** changes the interface language. See [Themes and language](/freelucy/personalize-and-accessibility/themes-and-language.md).
* **User menu** shows the signed-in user and their roles.

## The view tabs

Switch how you see the record with the view tabs. Freelucy has three views: **Classic**, **Flow**, and **List**. Switch with the tabs or with the `Alt/Option` plus number shortcut for the view.

Your staged edits are shared across every view. Add a relationship in Flow, switch to Classic, and it is already there. See [Choose a view](/freelucy/get-started/choose-a-view.md).

<figure><img src="/files/c6cO3aGs0y8rdCfBtaMn" alt="" width="338"><figcaption></figcaption></figure>

## The Data Hub

The **Data Hub** is the drawer you pull records from. Open it to search suggested tables, browse a record tree, and add one or many records to your primary element. See [Find records with the Data Hub](/freelucy/work-in-the-app/data-hub.md).

<figure><img src="/files/dtcoeyR75WPeMCX93wP3" alt="" width="375"><figcaption><p>Data hub -- after selecting a table</p></figcaption></figure>

## The commit bar

Every change you make is staged first, never written straight to ServiceNow.

* The **pending-change count** shows how many edits are waiting.
* **Commit** opens a review dialog where you confirm each change.
* **Discard** drops every staged edit and refetches the record.

<figure><img src="/files/ZmsNpB6baPGBz45uqQmk" alt="" width="375"><figcaption></figcaption></figure>

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

***

## What's next

* [Choose a view](/freelucy/get-started/choose-a-view.md)
* [Find records with the Data Hub](/freelucy/work-in-the-app/data-hub.md)
* [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 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/get-started/tour-the-editor.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.