Document Types Management
Document Types Management defines the document catalogue used in Crewlap CVs and application document sections.
Administrators use this area to maintain document categories, groups, document types, subtypes, auxiliary types, field visibility, default labels, and validity rules. These settings affect what users see when they add or edit documents on an application.
Document Structure
Open Administration | Documents Structure to review the catalogue.
The structure contains several related sections:
Categories: the top-level document areas.
Groups: groups inside a category.
Auxiliary Types: optional extra choices available for a group.
Types: concrete document types selected by users.
Subtypes: optional choices under a document type.
Each section has a table. Use the plus button to create a new record, or open an existing row to edit it.
Category
A category defines a top-level document area.
The form includes:
Key: the stable category key.
Weight: the sorting weight.
Visibility: whether this category is shown to users.
translated category titles and descriptions.
Fill every language. If translations are not ready, repeat the same English value for each language until proper translations are available.
Group
A group belongs to a category and controls defaults for document types inside it.
The form includes:
Category: the parent category.
Key and Weight.
visibility settings for Type, Auxiliary Type, Subtype, Description, Issuing Authority, and Document Nr fields.
Default Validity Period.
translated labels and descriptions for the group and its fields.
Group defaults are inherited by document types unless a type overrides them.
Document Type
A type is the concrete document that a user selects on an application.
The form includes:
Group: the parent group.
Key and Weight.
Selected by Default.
field visibility settings for subtype, description, issuing authority, document number, country, and validity period.
Document Role.
Verification requirement: Required, Optional, or Not needed. New and existing types default to Optional.
field mapping options when the selected role enables them.
translated titles, descriptions, and field labels.
Change Document Role carefully. Roles are used by application behavior and are expected to stay unique where the business process requires a unique document role.
Use Required when operators must verify this document type, Optional when verification is useful but not mandatory, and Not needed when the document should not enter the verification process. This setting controls the initial status icon and whether an operator can start verification from the application.
Subtype And Auxiliary Type
A subtype belongs to a document type. An auxiliary type belongs to a document group.
Both forms use:
a parent selection;
Key;
Weight;
translated titles.
These values give users more precise choices when the related field is visible for a document type or group.
Saving Changes
Click Save after editing a document reference-data form.
If a validation message appears, fix the highlighted field and save again. Common causes are missing parent selections, missing keys during creation, or missing labels required by a visible field.
Good Practice
Keep keys stable after records are used.
Prefer updating labels and visibility over creating near-duplicate document types.
Be careful with visibility defaults because they change what users see in application document dialogs.
Review document role changes with the team that owns application document workflows.