Employee personal address should be private information
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Fix Committed
|
Low
|
OpenERP R&D Addons Team 1 |
Bug Description
The Employee Home address is a private and sensitive information.
Only HR professional should have access to it.
However, since it's stored in the Partners table, anyone can see these addresses.
Making these addresses inactive does not solve the issue: they can still be accessed using an Advanced Filter "Active is false".
From a information security point of view, this is a show stopper.
So, a proper solution is needed (using record rules?).
By the way, for the case where an Employee can also be a Customer, two solutions are possible:
* you just create a new Customer record, just like what you would do for a non-employee; or
* in the Work Address you use a Parter record specific for that Person.
Related branches
- Daniel Reis (community): Needs Information
- OpenERP Core Team: Pending requested
-
Diff: 57 lines (+17/-1)3 files modifiedhr/hr.py (+8/-0)
hr/hr_view.xml (+3/-1)
hr/security/hr_security.xml (+6/-0)
tags: | added: hr |
Changed in openobject-addons: | |
status: | Confirmed → In Progress |
Hello Daniel,
I agreed because payslip will be send at the home address of the employee. So its must be not accessed by the any other user.
Because If we using the hr_payroll_account modules and generate the accounting entry for the payslip then home address is passed on the journal item as a partner.
On OpenERPv7 we have removed the partner.address object and use the same object res.partner for the contacts and address both.
Thats why we have used the partner on home address field of the Employee.Also we can't put the restriction on access for the all partner for all users. So our sales/user or purchase/user able to update the partner record, here both have the same object so they can also able to update the employee's home address.
I have checked your both the solution but here both can't be feasible to solve the issue.
So currently I am setting this as a Wishlist because we need to improve this things and get the Opinion form community for the better solution.
Thanks for the reporting!