Document Management System
CMDBuild integrates with external Document Management Systems (DMS) to store and retrieve attachments associated with Configuration Items.
CMDBuild natively supports the open-source Alfresco DMS and Microsoft SharePoint. Additional DMS platforms can be integrated through custom plugins. PAT also provides a CMIS-compatible plugin to ensure backward compatibility with previous CMDBuild versions.
The DMS acts as the document repository, while CMDBuild provides the user interface used to upload, manage, and download attachments.
Attachments can be organized into document categories, which can be defined differently for each class. Each category can be associated with a document model, allowing administrators to configure specific metadata and behaviors.
DMS Models
DMS models allow configuring metadata associated with attachments. Their management follows the same logic as class configuration.
Properties Tab
The Properties tab is used to create new DMS models and manage existing ones.

Available operations:
- add a new DMS model
- search configured models and their attributes
- edit a DMS model
- delete a DMS model (physical deletion if empty, otherwise logical deletion)
- disable a DMS model
- print model details
Each DMS model includes a set of properties similar to class properties, with the addition of the Attachments Properties section.
Attachments Properties
This section allows configuring metadata and behaviors specific to the DMS model:
- Allowed extensions: file extensions permitted for attachments associated with this model
- Count check: validation based on the number of attachments
- No check
- At least number: minimum number of attachments required
- Exactly number: exact number of attachments required
- Max number: maximum number of attachments allowed
- Max file size: maximum allowed file size
Attributes Tab
Attribute management follows the same logic used for class attributes.
Layout Tab
Layout configuration follows the same logic used for class layouts.
DMS Categories
DMS categories allow defining document categories that can be assigned to one or more CMDBuild classes. Each category can be enriched with metadata through DMS models and additional configuration options.
Properties Tab
This tab displays the name of the selected DMS category.

Values Tab
The available sections are similar to those used for lookup lists, except for the Attachments Properties fieldset available for category values.

Attachments Properties
The following properties can be configured:
- DMS model: DMS model associated with the category value
- Allowed extensions: file extensions permitted for uploads in this category
- Count check:
- No check
- At least number
- Exactly number
- Max number
- Max file size: maximum allowed file size

Assigned On Tab
This section shows the classes and processes associated with the selected category.

Settings
This section allows configuring global DMS settings.

General
The following properties are available:
- Active: enables or disables DMS integration in CMDBuild
- DMS category: default category used by the system
- Service type: DMS service used for document management
- Alfresco
- Microsoft SharePoint
- Custom plugin

DMS Properties
This section allows configuring the connection parameters required by the selected DMS service.
Properties
The following global attachment settings are available:
- Attachments preview limit: maximum number of attachments for which a preview can be generated (0 = no limit)
- Advanced search using DMS API: enables document searches through DMS APIs; performance may vary depending on the DMS platform
- Auto resize image on upload: automatically resizes images during upload
- Image long side max size (px): maximum size of the longest image side after resizing

Attachments Validation
This section allows defining global validation rules for uploaded attachments. These settings are overridden by configurations defined in DMS Models or DMS Categories.
- Max file size: maximum allowed file size in MB
- Allowed extensions for attachments uploaded from the user interface: comma-separated list of allowed extensions (for example: pdf,odt,csv)
- Allowed extensions for incoming emails: comma-separated list of allowed extensions (for example: pdf,odt,csv)
