This addon creates a new kind of view and allows to define a folder related to a record.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you attach a document folder tree to any Odoo record (for example a customer or an employee) and view it directly inside the record form. Templates define which folders and files are created automatically for each new record.
This module adds a new kind of view called "DMS Tree" and a way to embed a document folder inside any record.
- Administrators create "Embedded DMS templates" (menu under DMS configuration) where they choose a model, a storage, an optional parent folder, a folder name format and access groups. Only one template per model is allowed.
- When a new record of that model is created, Odoo automatically creates the matching folder (and its subfolders and copied files) and links it to the record. The folder name can use expressions like {{object.display_name}}.
- An access group is generated automatically for each record, so only the right users can see its documents. If the template defines a user field, that user is added to the group; changing that user on the record updates the group.
- Deleting the record also deletes its folders and the auto-generated access group.
- The folder tree appears inside the record form (for example on the customer form) and in a dedicated "Documents" menu that shows storages and their folders, with preview, download and open actions.
- Checks prevent duplicate folders for the same record in a storage, require a record for root folders when the storage is linked to models, and keep storages consistent with their allowed models.
- Multi-company rules restrict templates and access groups to the allowed companies.
Depends on
Required by other modules
Menus it adds
Models and fields (8)
- ir.ui.view · extends an existing modeltype
- dms.storage · extends an existing modelfield_template_ids (File templated ids)
- res.partner · new model
- dms.directory · extends an existing modelparent_id
- dms.field.mixin · new modeldms_directory_ids (DMS Directories)
- dms.access.group · extends an existing modelcompany_id (Company), dms_field_ref (DMS field reference)
- dms.field.template · new modelname, model (Model name), model_id (Model), group_ids (Groups), company_id (Company), storage_id (Storage), user_field_id (User field), parent_directory_id (Parent directory), directory_format_name (Directory format name)
- ir.actions.act_window.view · extends an existing modelview_mode
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 6 confirmed, 3 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/dms.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0To use the embedded view in any module, the module must inherit from the mixin dms.field.mixin (You have an example with res.partner in this module).
Once this is done, in the form view of the model we will have to add the following:
<field name="dms_directory_ids" mode="dms_list" />In addition, it will be necessary to create an Embedded DMS template for this model.
- Go to Documents \> Configuration \> Embedded DMS templates and create a new record.
- Set a storage, a model (res.partner for example) and the access groups you want.
- You can also use expressions in "Directory format name", for example: {{object.name}}
- Click on the "Documents" tab icon and a folder hierarchy will be created.
- You can set here the hierarchy of directories, subdirectories and files you need, this hierarchy will be used as a base when creating a new record (res.partner for example).
Usage
Source · Odoo 18.0- Go to the form view of an existing partner and click on the "DMS" tab icon, a hierarchy of folders and files linked to that record will be created.
- Create a new partner. A hierarchy of folders and files linked to that record will be created.
No verified information in OCA: Installation.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.