This addon is a demo addon for the fs_folder module. It adds declare a new FsFolder field on the res.partner. From the partner form, you can create a folder. This folder is created by default into a subfolder of the Odoo file store.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Adds a Documents tab to the contact form where you can store and manage files in a folder linked to that contact. The folder is created automatically inside Odoo's file storage.
This module is a demonstration of the file-folder feature. It extends the contact (partner) form so that each contact can have its own folder of documents.
Where it appears: - On the contact form, a new "Documents" page is added inside the existing notebook (the tabbed area of the form). - That page shows a folder field where files can be stored and managed.
What it does:
- Adds a folder field to contacts (res.partner).
- Provides an action that initialises the folder: if the contact does not yet have a folder, one is created automatically in the underlying file storage.
Business rules and behaviour: - The folder is only created when the initialisation action is called and the contact has no folder yet; it does not overwrite an existing folder. - The folder lives inside Odoo's file store, so documents are kept with the contact record.
Areas touched:
- Contacts (res.partner) and the contact form view.
Because this is a demo module, it mainly shows how the folder field can be placed on a form and initialised; it does not add menus, reports, emails or scheduled jobs.
Depends on
Models and fields (1)
- res.partner · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/storage.
terminal Installation and usage
No verified informationInstallation 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.