This module allows to create a personal equipment request and manage allocation of employee personal equipment.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets HR staff and employees create personal equipment requests, allocate items such as laptops or phones to employees, and track each allocation through draft, accepted, valid and expired states.
This module adds a Personal Equipment area under the Employees menu with two screens: Personal Equipment Request and Allocations.
- Users create a request for an employee (defaulting to their own employee record) and add lines of products. Only products flagged as "Is Employee Personal Equipment" can be selected, and the unit of measure is filled automatically from the product.
- HR officers can press Accept on a request, which moves the request and all its lines to Accepted. Cancel moves everything to Cancelled. Requests cannot be deleted once created.
- Each allocation line can then be Validated, which sets it to Valid and fills the start date with today if empty. A Valid allocation can be Expired, which sets the expiry date to today if empty.
- The employee form shows two counters (PE Request and PE) that open the related requests and allocations, grouped by state.
- Products gain an "Is Employee Personal Equipment" checkbox on the product form and in the supplier information section.
- Security rules let regular users see only their own employee's requests and equipment, while HR officers see everything. Allocations can only be deleted while still in Draft.
- Both requests and allocations use the chatter, so messages and activities are logged.
Depends on
Required by other modules
Models and fields (4)
- hr.employee · extends an existing modelequipment_request_ids, personal_equipment_ids, equipment_request_count, personal_equipment_count
- product.template · extends an existing modelis_personal_equipment (Is Employee Personal Equipment)
- hr.personal.equipment · new modelname, state, quantity, product_id, start_date, employee_id, expiry_date, product_uom_id, equipment_request_id
- hr.personal.equipment.request · new modelname, state, line_ids (Personal Equipment), employee_id (Employee), observations, allocations_count
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: 7 confirmed, 2 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/hr.
terminal Installation and usage
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0First, products which can be requested by employees should be marked as employee personal equipment. 1. Go to Products (In Inventory App for example). 2. Select a product. 3. Mark the Is Employee Personal Equipment flag.(An additional page appears which serves as a hook if additional fields are needed).
To create a personal equipment request, a common user should follow the next steps: 1. Go to menu Employees -\> Personal Equipment-\> Employee Personal Equipment Request 2. Current employee is set as default. (An Hr Officer can change the employee if needed). 3. At Personal Equipment select the equipments you want to request. 4. Add "Observations" at Observations if desired.
Then, an HR Manager should: 1. If everything is correct, "Accept" the request. 2. Finally, when the equipment is given to the employee, the allocation should be validated. This can be done in two ways: a) Click the allocation in the equipment request that you want to validate, the form view will be opened, and click "Validate". b) Go to Employees -\> Personal Equipment-\> Allocations. Select the corresponding allocation and click "Validate".
A common user can only see its own allocations. The HR Officer can see all of them.
If needed, the allocation can be expired clicking the button "Expire", which can be found at the allocation form view.
No verified information in OCA: Installation, Configuration.
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.