> 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/choose-a-view.md).
# Choose a view
YouDesign Freelucy shows the same record three ways. Every view edits the same record and shares the same staged changes, so you can switch whenever one fits the task better. Use the view tabs or the `Alt/Option` + (1-3 number) shortcut for the view.
## Classic
The original canvas. Your primary element sits in the center with its relationships radiating out as connected nodes. Best for a spatial sense of a record's immediate neighborhood and for users who already know the Classic editor.
[Open the Classic view guide](/freelucy/views-in-depth/classic.md)
## Flow
A two-column layout: upstream on one side, downstream on the other, with the primary element between them. Each column has search, and grouping, sorting, and type filters come from the shared View Controls drawer. Best for working through long relationship lists quickly and for precise add, update, and remove actions.
[Open the Flow view guide](/freelucy/views-in-depth/flow.md)
## List
A fast, scannable table of the record's relationships, grouped into upstream and downstream, with search and bulk editing. Best for working through a long relationship set and editing several at once.
[Open the List view guide](/freelucy/views-in-depth/list.md)
{% hint style="info" %}
**Your last view is remembered.** Freelucy keeps your view choice per table, so the next record you open in that table starts where you left off.
{% endhint %}
***
## What's next
* [How relationships work in Freelucy](/freelucy/work-in-the-app/usage.md)
* [Find records with the Data Hub](/freelucy/work-in-the-app/data-hub.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/choose-a-view.md?ask=&goal=
```
`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.