The Document types page

Configuration → Document types. Your own types are listed first, then every built-in group.
Turning a type off
Every type is on until you turn it off, except the types in the Fintech Partner Banking group. Those start off unless your organization already uses them, and turning one on turns on only that type. Turn off the types your organization never collects, so detection has fewer wrong answers to choose from and pickers stay short. To turn off one type, click its switch. To turn off several, select their rows and click Turn off in the bar at the bottom of the page.
Select rows to turn types off, turn them back on, or delete custom types in one step.

The confirmation says how many documents already carry the type. They keep it.
- New uploads are never detected as that type.
- It leaves the type pickers and the document filters.
- Documents that already have the type keep it and stay searchable. Coverbase reclassifies nothing.
Creating your own document type
Create a custom type when your vendors send something Coverbase does not have a type for, for example a Modern Slavery Statement, a Source Code Escrow Agreement or a Tabletop Exercise Report.Open the drawer
Name it
Add examples
Review how to recognize it
Create and check

The drawer drafts the description and suggests a group from your examples.
Writing a good description
A good description says what the document is, what is usually in it, and what it is not. The “not” sentence matters most when a built-in type is close.The detection check
Coverbase checks a custom type in the background after you create it and whenever you change its examples or description. A check takes 1 to 2 minutes, and the page updates on its own.
While the check runs, the page says so and the examples show as checking.
- Does it recognize your examples? Coverbase classifies each example against every type, leaving that example out of what detection learned from. A pass means detection would recognize a new file like it.
- Does it pull in documents that belong elsewhere? Coverbase classifies up to nine of your recent documents of the closest built-in types. Any that would now be detected as your new type are look-alikes.

A clean result: every example recognized, nothing pulled in.
Reviewing look-alikes
Open the type to see each look-alike, the type it has today, and what it would become. For each one, choose:- Keep as …: the document is not your new type. It keeps its current type.
- It is a …: the document really is your new type. Coverbase changes its type now.

One look-alike to decide on, and a suggested sentence that would keep failover tests out.
Testing a single file
To see which type a file would get, drop it into Try a file at the bottom of a custom type’s page. Coverbase detects its type exactly as it would for an upload and shows the result. Coverbase does not save the file.
Try a file shows which type a file would get, without saving it.
Changing or deleting a custom type
From a custom type’s page:Where custom types appear
A custom type works like a built-in type everywhere Coverbase uses document types:
A reminder for a custom type counts from the document's expiration date.

Document Insights coverage lists a custom type by name, with the insights scoped to it.
Examples
A bank that collects beneficial ownership forms. The compliance team creates Beneficial Ownership Certification with four completed FinCEN certification forms from different vendors. The check recognizes all four and finds no look-alikes among their business registration documents. Analysts stop relabelling these forms by hand. A team that runs tabletop exercises with vendors. They create Tabletop Exercise Report from six after-action reports. The check recognizes every example but pulls in one disaster recovery failover test. They click Keep as BC/DR Test Report, apply the suggested sentence about RTO and RPO tests, and the re-check comes back clean. A software company that never collects insurance certificates. On the All tab they search “Insurance”, select those types, and click Turn off. Those types leave every picker, and detection can no longer choose them.Manage types from MCP or the API
You can turn types on or off and create your own from an MCP client or with an API key. An MCP client reads withquery_platform(kind="document_types") and writes with mutate(entity="document_type", action="set_enabled") and mutate(entity="custom_document_type", action=...) (draft, create, add_examples, update, decide_lookalike, archive). To turn on an optional document type group, use query_platform(kind="document_type_groups") and mutate(entity="document_type_groups", action="enable"), or GET /v1/document-type-groups and POST /v1/document-type-groups/enable. The API routes are POST /v1/document-type-settings/set-enabled and the /v1/custom-document-types routes. See Document types.
Before an MCP client sends a write, it shows you the change and waits for you to confirm it. The MCP tool reference lists every field.
These calls need organization settings permission. API keys do not hold it, so use a key created by a person whose role holds it. The API has no route to delete a custom type. Do that in the dashboard or through MCP.