> 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/fields/add-and-configure-fields.md).
# Add and configure fields
Use a stored field for a value you enter, a computed field for a calculation, or a related field for data linked from another table.
## Add a field in Jet Tables
1. Open **Data**, select your Jet Tables resource, and open the table.
2. Select **Add field** at the right end of the column headers.
3. Choose **Add new field**.
4. Set the name and a type that matches the values you will store, then complete the field configuration.
5. Enter a sample value in a test record. Reopen it and confirm that the value and format are correct.
Choose a stored field or one of the available calculated-field options.
Example configuration for a Number field. This screenshot shows the form before creation.
The same menu includes computed fields, lookups, rollups, and AI autofill. See [Computed fields](/user-guide/data/computed-fields.md) and [Relationships](/user-guide/data/relationships.md).
For connected data, update the source schema where required, then [sync schema changes](/user-guide/synced-tables/sync-schema-changes.md). Changing a component's display format does not change the source column type.
## Configure columns in Classic App Builder
Select the table component and configure the column's display type. For example, use an image display for a field containing image URLs. Check a record with a value and a record with an empty value.
Reorder columns to match your task, and hide fields that do not need to appear in the component. Hidden fields remain in the data source; use permissions to control access.
For Data Editor view controls, follow [Navigate the Data Editor](/user-guide/data/navigate-the-data-editor.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.jetadmin.io/user-guide/data/fields/add-and-configure-fields.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.
