Document Type Master
The Document Type Master defines the categories you use to classify uploaded documents — for example Sale Deed, Encumbrance Certificate, Patta / Chitta, Layout Approval, or ID Proof. When someone uploads a file anywhere in the system, they pick a document type so the document is filed and findable.
Where to find it: Masters → Document Type.
:::tip Configure before uploading documents A document cannot be uploaded without a type to classify it under. Set up the document types your organization works with before your team starts attaching files to stocks, projects, units, or parties. :::
What a document type holds
| Field | Required | Notes |
|---|---|---|
| Name | Yes | The document type's name (for example Sale Deed). Unique within your organization, case-insensitive and trimmed — Sale Deed and sale deed are treated as the same. |
| Active | Yes | Whether the type can be chosen for new uploads. Defaults to Active. |
| Custom Fields | No | Per-type attributes that documents of this type will capture (see below). |
Per-type custom fields
Document types support the Custom Fields system, letting each type capture metadata appropriate to it. For example:
- A Sale Deed type might define Registration Date (DATE) and Document Number (TEXT).
- An Insurance Policy type might define Expiry Date (DATE) and Renewable (BOOLEAN).
- An Approval type might define Issuing Authority (DROPDOWN).
When a user uploads a document and selects its type, the form renders that type's custom fields and stores the entered values with the document (as the JSONB custom_field_values array described in the overview). The standard rules apply: field type is fixed once created, DROPDOWN fields need their options, and removed fields are inactivated rather than hard-deleted.
Managing document types (CRUD)
- Add. Enter a name, set Active, optionally configure custom fields, and Save. Required-field and duplicate-name validation runs on submit.
- List. The list supports search by name and sorting by name or status.
- Edit. Rename, toggle Active, and adjust custom fields.
- Deactivate. An Inactive type is removed from the picker shown on new uploads, but documents already classified under it still resolve and display correctly — historical classification is preserved.
- Delete. Deletion is guarded: a document type that is referenced by any uploaded document cannot be deleted (the reference is enforced at the database level with a restrict rule). Unreferenced types are soft-deleted.
:::note Inactive still resolves historically Deactivating a document type is the safe way to retire it. Existing documents keep their type and remain searchable; only new uploads stop offering it. This is preferable to deletion, which the system blocks anyway once the type is in use. :::
How document types are used
Document types are referenced by the centralized Documents module and anywhere files are attached (stocks, projects, subprojects, units, parties). Choosing a consistent, well-named set of types up front pays off later when you filter and report on documents by type.
Related
- Reference Data Overview — the custom fields system
- Status Master — statuses can optionally link to a document type
- Documents — where documents are uploaded and classified