> 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/fields.md).

# Fields

The **Field Settings** page of a document type lists every field DocBits extracts or stores for that type. Here you decide which fields validation needs, how much recognition confidence each one requires, and which formula calculates a field that is not extracted. Open the page from the card of the document type: **Settings → Document Types**, then **Fields** on the card.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-99554f58e4888cbaad11ffdcc90a5820414fdbd7%2Ffield-settings-page-en-20261031.png?alt=media" alt="Field Settings page of the Invoice document type with the recognition sliders at the top and the Invoice details field group below"><figcaption><p>The <strong>Field Settings</strong> page of the Invoice document type. The switches and thresholds in a row apply to that one field.</p></figcaption></figure>

## Overview

Each field can be adjusted to optimize the accuracy and efficiency of data capture and validation. A change on this page applies to the document type only; other document types keep their own field settings.

## What the page controls

* **Recognition settings**: the **OCR** and **MATCH SCORE** sliders at the top are the default for every field of the document type. A field can override both values in its own row. **Restore defaults** puts the two sliders back to the values DocBits ships with.
* **Field groups**: the fields are grouped by area of the document, such as *Invoice details*, *Payment details* and *Purchase order*. **Create field** in a group header adds a field to that group, **Create new group** adds a group of your own.
* **Search by Name**: filters the list while you type.
* **Save Settings**: writes the changes of the whole page. Nothing on the page is applied before you click it.
* **Master Data Settings**: opens the lookup master data of the document type.

## The columns of a field row

* **Fields**: the technical name of the field in small print, with the name users see underneath. Click the field to open its **Document field details**.
* **REQUIRED**: the document cannot finish validation while the field is empty.
* **Read Only**: the value is shown but cannot be edited during validation.
* **Hidden**: the field is not displayed in the interface.
* **FORCE VALIDATION**: the value must pass the validation rules of the field before the document can be validated.
* **Use AI**: whether the AI extraction fills the field. **Default** follows the setting of your organisation, **Yes** and **No** force the behaviour for this field. The end of each option (**requested** / **not requested**) says what the extraction currently does with the field.
* **OCR** and **MATCH SCORE**: thresholds for this one field. Leave them empty to use the recognition settings at the top of the page.
* **FORMULA**: for a calculated field, the **+** button opens the formula.

The checkbox in a column header switches that column on or off for every field of the document type at once.

## Editing a field

1. Click the field name. The **Document field details** dialog opens.
2. Change the title, the switches or the advanced options. The name and the data type of an existing field cannot be changed.
3. Click **Save** in the dialog, then **Save Settings** on the page.

To move fields to another group, tick them in the first column and choose **Reassign field group** from the ⋮ menu in the table header.

{% hint style="info" %}
Adding a field, including a field that carries a charge, is described step by step on [New Fields with Charges](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields/new-fields-with-charges.md). The dialog itself is covered on [Adding and Editing Fields](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields/adding-and-editing-fields.md).
{% endhint %}


---

# 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.docbits.com/administration-and-setup/settings/global-settings/document-types/fields.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.
