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

# Activation

Administrators can choose which document types are available to their organization. You can change this on the **Document Types** page without deleting the type or its configuration.

1. Open **Settings → Document Types**.
2. Find the document type, for example **Invoice**, under **Default Document Types** or **Custom Document Types**.
3. Use the switch labelled **Activate** on that type's card. A colored switch means the type is active; a gray switch means it is inactive. Wait for the confirmation message before leaving the page. There is no separate Save button for this switch.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-5de56fe79cbf6f26088ac332636fade3304e340c%2Fprior-t019-en.png?alt=media" alt="Document types and activation options."><figcaption><p>Document types and activation options.</p></figcaption></figure>

The **Extraction** switch beside **Activate** is a different setting. It selects the extraction mode (Flex or Fix); it does not activate or deactivate the document type. The gear icon opens more settings for that type. The links below the type name open its layouts, fields, tables, scripts, and other available configuration areas.

DocBits provides the default document types, which cannot be deleted. You can also create and manage custom types. See [Adding and Editing Document Types](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/adding-editing-document-types.md) for the next setup steps and [Table Columns](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/table-columns.md) to configure extracted line items.


---

# 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/activation.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.
