> For the complete documentation index, see [llms.txt](https://documentation.siteglide.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.siteglide.com/developer-tools/configuration/field-types.md).

# Field Types

## Field Types available

A list of field types available on Siteglide and the corresponding platformOS data type applicable to them

| Name                     | Siteglide Type    | platformOS Type |
| ------------------------ | ----------------- | --------------- |
| Text (String)            | input\_text       | string          |
| Text (Multiline)         | textarea          | string          |
| Checkbox                 | input\_checkbox   | array           |
| Radio Button             | input\_radio      | string          |
| Dropdown (Single Item)   | select            | string          |
| Dropdown (Multi Item)    | select\_multi     | array           |
| Datasource (Single Item) | datasource        | integer         |
| Datasource (Multi Item)  | datasource\_multi | array           |
| Image (Single)           | image             | string          |
| Image (Array)            | image\_array      | array           |
| File                     | file              | string          |
| Folder                   | folder            | string          |
| Date                     | date              | integer         |
| Number (Integer)         | number\_integer   | integer         |
| Number (Float)           | number\_float     | float           |
| Boolean                  | boolean           | boolean         |
| Custom Array             | array\_custom     | array           |

## Where are these field types available to use as Custom Fields?

* **Modules** - All field types
* **WebApps** - All field types
* **eCommerce Products** - All field types
* **CRM Users** - All field types
* **Forms** - All field types *except Custom Array*
* **Custom Field Sets** - All field types *except Custom Array*

## Form Configuration metadata options

All field types have the following metadata options:

| Name     | Type    | Notes                                                                                             |
| -------- | ------- | ------------------------------------------------------------------------------------------------- |
| name     | string  | The field name to be shown in Siteglide Admin UI                                                  |
| type     | string  | The field type in the 'Siteglide Type' column above                                               |
| live     | boolean | Determines whether or not the field is shown or used anywhere                                     |
| hidden   | boolean | Determines whether or not the field is shown in Siteglide Admin UI                                |
| order    | integer | The position the field is shown in Siteglide Admin UI and Import CSVs                             |
| editable | boolean | Determines whether you can edit this metadata in the Siteglide Admin UI builder views             |
| required | boolean | Determines whether it is required to fill in this field in Siteglide Admin UI and front-end forms |

Some other metadata options are available to specific field types:

| Name           | Type    | Available for                                     | Notes                                                                                                                                   |
| -------------- | ------- | ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| rich\_text     | boolean | textarea                                          | Determines whether the Rich Text editor appears in Siteglide Admin UI for this field                                                    |
| options        | string  | input\_checkbox input\_radio select select\_multi | A comma separated string of options to be displayed for this field in Siteglide Admin UI                                                |
| datasource\_id | string  | datasource datasource\_multi                      | The ID of the model you want options to show from for this field in Siteglide Admin UI. This includes the type, for example `webapp_1`. |
| num\_min       | string  | number\_integer number\_float                     | The minimum value this number field will allow the user to select.                                                                      |
| num\_max       | string  | number\_integer number\_float                     | The maximum value this number field will allow the user to select.                                                                      |
| num\_step      | string  | number\_integer number\_float                     | The amount the number will change by using the number scroller in Siteglide Admin UI.                                                   |
| num\_precision | string  | number\_integer number\_float                     | The amount of decimal places shown in Siteglide Admin UI.                                                                               |


---

# 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://documentation.siteglide.com/developer-tools/configuration/field-types.md?ask=<question>&goal=<user_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.