This module introduces the following features:
- Adds the Operating Unit (OU) to the Employee Contract.
- Security rules are defined to ensure that users can only see the Contracts of that Operating Units in which they are allowed access to.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Adds an Operating Unit field to employee contracts and restricts which contracts each user can see based on the operating units they are allowed to access.
This module links employee contracts to an Operating Unit, a way of splitting a company into separate business units. On the contract form, a new Operating Unit field appears after the Job Position field, and it is also shown in the contract list and in the search filters. The field is only visible to users who belong to the multi operating unit group.
When a user creates a contract, the Operating Unit is filled in automatically with that user's default operating unit. The field only offers operating units the user is allowed to use, so it is not possible to pick an unrelated one.
A security rule is added on contracts: users can only read contracts that either have no operating unit or belong to one of their allowed operating units. This rule is global and read-only, meaning it does not grant write, create or delete rights by itself. As a result, contracts from other operating units are hidden from the user's contract lists and searches.
The module touches the hr.contract model and its existing form, list and search views. It does not add new menus or reports.
Depends on
Required by other modules
Models and fields (1)
- hr.contract · extends an existing modeloperating_unit_id
Text generated by AI (DeepSeek) from reading the Odoo 15.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: 4 confirmed, 5 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/operating-unit.
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.