> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/configuring-field-properties.md).

# Configuring Field Properties

## Configuring field properties is critical to ensure that the data captured in a document meets specific requirements and processing processes.

### Here are the steps to configure field properties to meet specific data processing needs:

#### Select a field type:

* Start by selecting the right field type for your data.

<figure><img src="/files/PIbmquJFcZdRq7QvOQol" alt="" width="375"><figcaption></figcaption></figure>

* This depends on what type of information the field will contain.

<figure><img src="/files/aMHthjgHvvtvKJhuGCg7" alt="" width="139"><figcaption><p>Properties</p></figcaption></figure>

* Possible field types include text, number, date, drop-down menu, checkbox, etc.

<figure><img src="/files/2y7sTRK7alqayioPecfB" alt="" width="241"><figcaption><p>Elements</p></figcaption></figure>

#### Set validation and formatting:

* Set validation rules to ensure that the data entered meets the expected criteria.
* This may include checking for certain string patterns, numeric limits, date formats, or other conditions.

<figure><img src="/files/3DXOseUaJ49Dnj81ASOm" alt="" width="236"><figcaption></figcaption></figure>

#### Define default values:

* If certain fields typically have a default value, you can set that as the default value.
* This makes data entry easier because users don't have to enter the same value every time.

<figure><img src="/files/ivIFzbQrh7F0Dc11PqhU" alt="" width="224"><figcaption></figcaption></figure>

#### Set user permissions:

* Determine which user groups should have access to the field and what type of access rights they have.

<figure><img src="/files/vzSrOHeBYjmBBTcw5Uoe" alt=""><figcaption><p>Settings: Groups and Permissions</p></figcaption></figure>

* This can include read, write, or edit rights.

<figure><img src="/files/UMu1J5SaxoXlYZpfOBVW" alt=""><figcaption><p>View Permissions</p></figcaption></figure>

#### Link to other data:

* In some cases, data from one field needs to be linked to data from another field or data source.
* Configure appropriate links or relationships to ensure consistent data integration.

#### Apply visibility rules:

* Determine under what conditions a field should be visible or hidden.
* This can be useful for dynamically adapting the user interface based on certain data or user actions.

<figure><img src="/files/XNwYcXgn71IVtHlDDIU8" alt=""><figcaption><p>Setting Fields</p></figcaption></figure>

#### Enable historization:

* If necessary, enable historization of fields to track changes historically.
* This allows you to track changes to the data and monitor the history of data changes.

#### Add documentation notes:

* Add notes or descriptions to explain to users how to use the field or what type of data is expected.

By following these steps and configuring the appropriate field properties, you can ensure that your documents meet specific requirements for data handling, user access, and data accuracy.


---

# 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.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/configuring-field-properties.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.