> 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/inspect-navigate-share.md). # Inspect, navigate, and share Inspect a relationship, jump to a connected record, open its form, and share the view. Beyond add, update, and remove, YouDesign Freelucy gives you a set of utilities for understanding what is on screen, moving between connected records, and sharing the result. These work across views, with small differences in where the controls live. ## Inspect a relationship To see what a relationship is, look at the relationship type Freelucy shows for it. In Classic, it will appear near of the connection between two elements. In Flow, the type is shown on each row, and you can filter a column by type.

## Open the ServiceNow form To open the underlying ServiceNow record form for any element, use the open-record action. In Flow it is **Open record**, on the row overflow menu and the central record card. In List it is **Open form**, on the row menu. In Classic it is on the element's context menu. The form opens in a new browser tab.

## Jump to a connected record To move the editor onto one of the connected records, making it the new primary element so you can map its relationships, use **Jump to**. The connected record becomes the center, and you can edit its upstream and downstream from there.

{% hint style="info" %} **Staged edits travel with you.** Jumping to another record keeps your staged changes. Freelucy warns you before you leave the editor entirely with uncommitted edits. {% endhint %} ## Export and share You can export what you see as an image. The export reflects the current view and includes staged edits, so it is a faithful picture of your work in progress.

{% hint style="info" %} **Exports honor your theme.** Export in dark mode and the image comes out dark. See [Themes and language](/freelucy/personalize-and-accessibility/themes-and-language.md). {% endhint %} For view-specific controls, such as Classic's layout and canvas filters or Flow's grouping and search, see the [view guides](/freelucy/views-in-depth/classic.md). *** ## What's next * [Classic view](/freelucy/views-in-depth/classic.md) * [Flow view](/freelucy/views-in-depth/flow.md) * [List view](/freelucy/views-in-depth/list.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/inspect-navigate-share.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.