> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.cloudraker.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server. # Project data A project collects its data as **records** — rows of a [record type](/record-types/overview) such as *Invoice* or *Vendor*. This page shows you how to open that data in a table, shape what you see with saved **Views**, and add or edit records by hand. People enter records by hand, and Florent writes them when it extracts data from documents — but AI-written values always wait for your review before they count (see [Reviewing AI work](/work/reviewing-ai-work)). This page covers the table, views, and manual editing. For what a record type is, where it lives, and the field types it can hold, see [Record types](/record-types/overview). ## Open the records table Each record type in a project has its own table of records. In a project, click the **Record types** tab. You'll see a table of the project's record types, each showing its **Name** and **Fields** count. Click a record type's name to open its **records table** — one row per record. The table header shows the record type's icon and name, an **Edit fields** button (which opens the schema editor — see [Build a record type](/record-types/build-a-record-type)), and a **New record** button. Below the header sits the [view toolbar](#shape-the-table-with-views), then the table itself. ### How to read the table * The columns come from the active view: which fields show, and in what order. The **Title** field is always pinned first. * Cells show formatted values — dates and currency formatted, **Select** and **Multi-select** shown as colored badges, **Boolean** as Yes/No, an address as a small block. * Click any row to open that record in a full panel. * A **Load more** button appears at the bottom when there are more records than the current page shows. Fields that Florent wrote may show a small status dot next to the value — **Approved** or **Rejected** — and a review control in the column header. That's [field review](/work/reviewing-ai-work), which is where you approve or correct AI output. This page is about the table itself. If a record type has no records yet, the table shows **No records yet** with an **Add the first record** button. ## Shape the table with views A **view** is a saved table layout: which columns show and in what order, plus filters and sorts. Set up a view once and the whole team gets it — every view is shared with everyone who has access to the project. There are no private, per-person views. The toolbar across the top of the table holds everything you need to switch and shape views. ### Switch views The view switcher on the left shows the active view's name. Open it to pick another view. Every project starts with one default view, always named **All records**, plus any custom views the team has created. Picking one re-lays the table instantly. ### Filter to the records you need Click **Filter** to open the filter builder. It shows a count when filters are set, like **Filter (2)**. Click **Add filter**, pick a **field**, pick a **condition**, then enter a value. Conditions include **Is**, **Is not**, **Is empty**, **Is not empty**, **Contains**, **Does not contain**, **Greater than**, **Less than**, **Is before**, **Is after**, and more — the list adapts to the field's type. Add more rows for more conditions. With more than one, a **Match** dropdown appears: choose **All conditions (AND)** to require every condition, or **Any condition (OR)** to match any of them. Click the trash icon on a row to drop it. Some field types — currency, email, phone, URL, and address — can't be filtered or sorted in this version. They won't appear in the field picker. ### Sort the rows Click **Sort** to order the rows. Click **Add sort**, pick a **field**, then a direction — **Ascending** or **Descending**. Add more sorts to break ties; they apply in order. With no sort set, records show newest first. ### Show, hide, and reorder columns Open the **"…"** options menu and choose **Fields** to open the columns panel. * Each visible field has a checkbox — uncheck it to hide that column — and a drag handle to reorder it. The order here is the order columns appear in the table. * Open **Hidden fields** to bring a hidden column back. * The **Title** field is pinned first and can't be hidden or moved. Filter, sort, and column changes save to the active view automatically as you make them — there's no separate save step. ### The "…" options menu The **"…"** button next to the toolbar opens a few more actions: * **Default View** — jump back to the **All records** view. * **Fields** — open the columns panel above. * **Create custom view** — start a new saved view. * **Copy link to view** — copy a link that opens the table on the exact view you're looking at. * **Delete view** — delete the current custom view (the default view can't be deleted). ### Create a custom view To save a layout your team can return to, create a custom view. From the **"…"** menu, choose **Create custom view**. The new view starts from your current columns, filters, and sorts, so set those up first if you can. Give the view a **Name** — something like *Open this week* — then click **Create view**. You're switched straight into the new view, where you can keep adjusting its filters, sorts, and columns. ### Share a specific layout There's no separate share step — views are already shared with everyone on the project. To point a teammate at a particular layout, open that view and use **Copy link to view**. The link opens the table on that exact view. Switching views and copying links are open to everyone. Creating, editing, or deleting views needs the right permission — Members can browse views but can't change them. See [Roles and permissions](/admin/roles-and-permissions). The default **All records** view can't be renamed or deleted. You can still change which columns it shows. ## Add a record by hand You can enter records directly, without waiting for Florent. From the records table, click **New record** (or **Add the first record** on the empty state). A **New record** dialog opens. Each field uses the control that fits its type — a text box, a number, a currency amount, a Yes/No switch, a date picker, a **Select** dropdown, **Multi-select** tags, and so on. Required fields are marked with a red asterisk (\*). Click **Create record**. If something's wrong — a required field is empty, or a value isn't valid — an inline error points you to it. Once it saves, the new record opens in its panel. ## View and edit a record Click any row to open the record in a full panel. The header shows the record's **Title** value (or *Untitled* if it's blank). Fields are grouped into sections, and the panel has two panes: the **Fields** pane on the right, and a **Source document** pane on the left that shows the source behind AI-extracted values. For a record you entered by hand, the left pane just says *"Select a field's cited source to preview it here."* ### Edit a field Click a field to edit it in place. Its control appears with **Save** (check) and **Cancel** (X) buttons. Click **Save**. Only that field is updated — every other field is left untouched. To empty an optional field that holds a value, use the **Clear** (trash) button on it. Required fields have no **Clear** button — they must always hold a value. Fields that Florent wrote carry a citation and per-field review controls so you can check the AI's value against its source before approving it. That's covered in [Reviewing AI work](/work/reviewing-ai-work). Deleting a record is a separate permission from editing. Members can add and edit records but can't delete them. See [Roles and permissions](/admin/roles-and-permissions). ## Where to go next What a record type is and where it lives. Shape the fields each record captures. Approve and correct the values Florent extracts. Who can edit records, delete them, and manage views.