> 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/design-and-structure/components/fields.md).

# Fields

Fields are single record data obtained from your resources. By default, all fields from your resource will be rendered as a text, but you can switch to a more appropriate one.

For example, you have a table of your customer's details, you can click on a record to see all available fields. All records from the same collection share the same fields. For example, each customer will have a specific `Firstname`, `Lastname`, `Email`.

![](/files/-MFesczP0oC2Y9lMdHgD)

### Customize your fields

Your fields are what contains your data. They belong to a collection, so in order to customize them, go to Visual Builder and choose which field you will customize.

![](/files/-MFetky9y-JLO75iqQgh)

### Field Types

By default, all fields from your resource will be rendered as a text - this is the most basic way to display your content (depending on your field type). But if you need to change your field type, you can set it up manually. For example, if your contacts have a field with a phone number, you can change the type of field to Integer.

![](/files/-MFeum1vpCnBrO5pRzeJ)

### Field Data

You can get the value of the selected record in the component by configuring the parameter transfer. For example, you want to display the `email` of the selected user.

![](/files/-MG5ub77PaSFfzBTd1gE)

### Additional Parameters

More information about Additional Parameters in our documentation.

{% content-ref url="/pages/-MA3icbYzG8h73uN2xMD" %}
[Broken mention](broken://pages/-MA3icbYzG8h73uN2xMD)
{% endcontent-ref %}


---

# 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.jetadmin.io/user-guide/design-and-structure/components/fields.md?ask=<question>&goal=<endgoal>
```

`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.