> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/data/records.md).
# Records
Work with records after connecting a source or creating a Jet Database.
1. Open **Data**, select your resource, then select its table or collection.
2. Use **Search**, **Filter**, and **Sort** to find the records you need.
3. Open a record or cell to inspect its values. Available editing actions depend on the resource and permissions.
4. After an edit, reload the record and verify the saved value. For an external source, check that source when validating write behavior.
For spreadsheet-style editing, see [Navigate the Data Editor](/user-guide/data/navigate-the-data-editor.md). For changes across records, see [Bulk edits and actions](/user-guide/data/records/bulk-edits-and-actions.md).
A filtered view changes which records you see. It is not an access-control rule.
## Add a record in Jet Tables
1. Open the table and select **New Record**.
2. Enable the optional fields you want to fill in.
3. Enter the values and select the form's create button.
4. Find the new record in the table and reopen it to verify the saved values.
The Tickets template example below shows the **Create Tickets** button. The table name depends on the collection you selected.
Enable the fields you need, enter their values, and select Create Tickets.
The saved demo ticket has ID 1, the entered name, and Low priority.
---
# 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.jetadmin.io/user-guide/data/records.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.
