> 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/adding-editing-document-types.md).

# Adding/Editing Document Types

Administrators can create a custom document type or change the settings of an existing one. Open **Settings → Document Processing → Document Types**. The page separates the built-in **Default Document Types** from **Custom Document Types**.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-6f2777cb8b5c3aba16475dd7c6511faef402cacc%2Fdocument-types-overview-en-20261104.png?alt=media" alt="The Document Types page: the Default Document Types section with the Invoice card, which has Activate and Extraction switches, the More Settings gear and the links Layouts, Fields, Tables, Validation Rules, Transformation Rules, Scripts, Model Training, E-Doc, Document Sub Types and Logs; the other cards show fewer links."><figcaption><p>Use a document type card to open the setting you want to change. The Invoice card offers the most links because validation and transformation rules are enabled for it.</p></figcaption></figure>

## Create a custom document type

1. Scroll to **Custom Document Types** and select **+ New**. The default types supplied by DocBits cannot be deleted; create a custom type for a new category.
2. On **Create**, enter a clear **Name** and a **Description**. Select **Table available** if this document type needs line-item tables. Choose **Auto** for model training with sample documents or **Regex** for pattern-based recognition.
3. Select **Next** to create the document type and continue the setup. **Next saves the new type at this point**; it is not just a preview. Avoid entering a test name in a production organization.
4. For **Auto**, upload at least **10 sample documents** before continuing. For **Regex**, create at least **two patterns**. These requirements come from the current creation flow. See [Model Training](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/model-training.md) for training details.
5. Under **Fields & groups**, create the groups you need and at least one field. If **Table available** was selected, continue to **Tables & columns** and configure the table. Select **Finish** when the required setup is complete.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-3012e66b55330f0b4d5e81f4fc4bff8ed345d769%2Fdbdc180-custom-new-en.png?alt=media" alt="Custom Document Types section with the New button"><figcaption><p>The New button starts the custom document type wizard.</p></figcaption></figure>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-3247a83ff5c03c6c7d285ad8e71a4a66cd5339a9%2Fdbdc180-create-form-en.png?alt=media" alt="Create New Document Type form with Name, Table available, Description, Auto, Regex and Next controls"><figcaption><p>Choose the type and recognition method before selecting Next.</p></figcaption></figure>

## Edit an existing document type

Find the type's card under **Default Document Types** or **Custom Document Types**. The controls on each card have different jobs:

| Control                  | What it does                                                                                                                                                                                                                          |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Activate**             | Turns processing for this document type on or off. Check the current state before changing it.                                                                                                                                        |
| **Extraction**           | Switches between the **Flex** and **Fix** extraction modes; it does not activate or deactivate the document type. Hover over the switch to see the current mode.                                                                      |
| **Settings** (gear)      | Opens **More Settings** for that document type.                                                                                                                                                                                       |
| **Layouts**              | Opens the validation layout. See [navigating the Layout Manager](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/layout-manager/navigating-the-layout-manager.md).                          |
| **Fields**               | Opens field configuration. See [adding and editing fields](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields/adding-and-editing-fields.md).                                            |
| **Tables**               | Opens table columns for this document type.                                                                                                                                                                                           |
| **Validation Rules**     | Opens the [custom validation rules](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/custom-validation-rules.md) of this document type. Shown when the rule manager is available.            |
| **Transformation Rules** | Opens the [transformation rules](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/transformation-rules.md) of this document type. Shown when the rule manager is available.                  |
| **Scripts**              | Opens processing scripts when that feature is available.                                                                                                                                                                              |
| **Model Training**       | Opens training data and model options.                                                                                                                                                                                                |
| **E-Doc**                | Opens electronic document settings when available. See [E-Doc settings](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi.md).                                                            |
| **Document Sub Types**   | Opens subtype settings; see [Document Sub Types](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/document-sub-types.md).                                                                    |
| **Logs**                 | Opens the rule execution logs of this document type, one row per evaluated rule; see [Custom Validation Rules](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/custom-validation-rules.md). |

The links shown on a card depend on the organization's enabled features and the document type. Open the relevant section, make the intended change there, and check a sample document in the validation view before using the updated type in regular processing.


---

# 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/adding-editing-document-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.
