Project Multi Department Classification
This module allows to assign Departments to Projects. The default security rules allow members of departments to access the department related projects and tasks
If you want to assign only one department to projects you might like project_department module
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you tag projects with one or more HR departments, and automatically gives employees access to projects and tasks of their own department (and its sub-departments).
This module links projects to HR departments. On the project form, a new "Project Departments" field appears right after the project manager, where you can pick several departments as tags. When a user creates a project, the field is pre-filled with the department of that user's employee record.
Tasks do not store their own departments: they simply display the departments of their project, so the classification stays consistent.
The departments are also visible in the project list view, and in the project search you can filter on departments or group projects by department.
A business rule controls who sees what. For projects and tasks that are not restricted to followers only, users see the ones linked to their own department or to a sub-department, plus the ones with no department at all. Projects and tasks marked as visible to followers only are not affected by this rule.
In short: departments become a way to organise projects and to share them automatically with the right teams, without manually adding each person.
Depends on
Models and fields (2)
- project.task · extends an existing modeldepartment_ids
- project.project · extends an existing modeldepartment_ids (Project Departments)
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/project.
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.