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

# Configure subtypes

Configuring subtypes allows you to customize the structure and behavior of the documents within a specific type. Here is an explanation of how you can use the "Fields", "Edit Layout", and "Scripts" options to customize each subtype to specific needs:

* **Fields:** The "Fields" option allows you to add, edit or remove custom metadata fields for the subtype. These fields can contain information about the documents of that type such as title, author, date, category, etc. You can use different field types such as text boxes, dropdown lists, date values, etc. to capture the data according to your requirements.

<figure><img src="https://lh7-us.googleusercontent.com/M1uaFb0tg0q-xh941cnEZgUOHbRzlOm8MgR0Mz-oeXun4Eyf45YZD-APOVUyMhJY1FmTwBqy0hTVdTGCcvXX47dDSjH8tTwybFkXr2_73G0lQk9xNXBZgdsZ7_QACEEDTiPxSARrGV3s-isT1AoO8Co" alt=""><figcaption></figcaption></figure>

* **Edit Layout:** The Edit Layout option allows you to customize the appearance and arrangement of fields on the user interface. You can change the order of fields, create groups of fields to group related information, and adjust the size and position of fields on the page. This allows you to optimize the user experience and improve usability.

<figure><img src="https://lh7-us.googleusercontent.com/thrOOaF54hZqhl1XVvgZfT1Hu4NOS1550gA9EmksjGaKTMLfKCEQct-OIM8e2qDh0E9Y9K8yf9CJ8kv1jmxgWSbqnAnk9dJpqA-fEhhU2scaMiR-xkcK_UFfiaSffvXb7e1Uvt-_y7U6fr9gAccJtfM" alt=""><figcaption></figcaption></figure>

* **Scripts:** The "Scripts" option allows you to add custom logic or automation for the subtype. You can use scripts to trigger specific actions when a document of this type is created, edited or deleted. This can be useful for implementing complex business rules, performing validations or integrating external systems.

<figure><img src="https://lh7-us.googleusercontent.com/G1SlZE44I3ZrL2cJYVpexKgxeyXYHxirnExRXGo2vqG-R4cXzabxd9oMai1I0qCerGc37UKxe6PF5OCbYkLyIdPbbOR0q9LyJJ1glTPOdD0_cQCNVZ-vB3z8VQYDpsIHJxXiZzT0gqht62zkD79fmw8" alt=""><figcaption></figcaption></figure>


---

# 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/configure-subtypes.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.