> 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/creating-a-new-sub-type.md).

# Creating a new Sub Type

Create a document subtype when one type of document needs its own field settings, validation layout, or scripts. You need access to **Settings → Document Types**.

## 1. Open the document type

Open **Settings → Document Types**. In the card for the relevant document type, select **Document Sub Types**. The example below uses **Invoice**; choose the type that matches your documents. Other links in the card lead to settings for the whole document type.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-5531d8086a2f0e500fd74e077d4bc525f52d8128%2Fcreating-subtype-invoice-card-native-en-20261103.png?alt=media" alt="Invoice card in the English Document Types settings, with the Document Sub Types link"><figcaption><p>Open subtypes for the document type you want to configure.</p></figcaption></figure>

## 2. Start a new subtype

On **Document Sub Types**, select **+ New**. Existing subtypes, when present, appear in the list; the three-dot **Actions** menu is for an existing row.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-1a357ca4923306518431db38e0d06d5bd11ccf01%2Fcreating-subtype-list-native-en-20261103.png?alt=media" alt="Empty English Document Sub Types list with the New button and Name and Actions headers"><figcaption><p>The list is empty in this test organization. Select + New to open the creation dialog.</p></figcaption></figure>

## 3. Name and save it

Enter a **Name** using letters and underscores, then enter a descriptive **Title**. Both fields are required. The screenshot shows the empty dialog before any values are entered. Select **Save** to create the subtype, or **Cancel** to leave without creating it.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-db16fe1b76cbd9eaeb5da9e2bc8058886c8d7da9%2Fcreating-subtype-dialog-native-en-20261103.png?alt=media" alt="Empty Create New Sub Document Type dialog in English with Name, Title, Cancel, and Save"><figcaption><p>The dialog is shown before entering values. Cancel closes it without creating a subtype.</p></figcaption></figure>

After saving, the new subtype appears in the list. To set its fields, layout, or scripts, open its **Actions** menu and follow [Configure subtypes](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/configure-subtypes.md). These settings are made after creation, not in the **+ New** dialog.


---

# 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/creating-a-new-sub-type.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.
