When creating an employee with a private contact,
the contact will not be automatically added to the employee's followers.

The desired behavior is that the contact is added
to the followers even if it has a private address.
Commit: 8760a4d0

However, this behavior will not be possible because
adding a contact with a private address is forbidden.
Commit: 20536e1b

Solution:
The solution is to use the private method `_message_subscribe`.
This is not a problem in the business case.
Indeed, the people who have access to the employee's file
also have access to the private contacts.
Moreover, the access rights of the public method `message_subscribe`
do not concern this business case.

opw-3249646

closes odoo/odoo#118572

Signed-off-by: Kevin Baptiste <kba@odoo.com>

The employee should be subscribed to their own record in order to
receive communication send to them.

closes odoo/odoo#84772

Taskid: 2749585
Signed-off-by: Kevin Baptiste <kba@odoo.com>

Steps to reproduce:
- set demo to receive notifs in Odoo
- go to employees
- click "launch plan" for demo user
- login as demo user
- Click on the link for the activity that is sent in discuss

Issue:
There is no chatter in the view

Explanation:
the view of en employee coming from messaging is always
hr.employee.public that does not contain the chatter.

opw-2990577

closes odoo/odoo#100959

Signed-off-by: Kevin Baptiste <kba@odoo.com>

Fields param is actually not a kwargs. This cause a stack trace when opening a chat window (other than a chat with yourself) from a Kanban user avatar icon.

closes odoo/odoo#100259

Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>

By enabling the method '_employee_values_sync' the original behavior is
keep. Furthermore, by overriding the method now is possible to decide
either a field is synced or not into employee.

closes odoo/odoo#96153

X-original-commit: 46c12cc0
Signed-off-by: Kevin Baptiste <kba@odoo.com>

Backport of odoo/odoo#81474
Before odoo/odoo#86889 a regular user with employees in multiple
companies was not able to change his own language due to a chain of
event calling onchange on all the employee_ids and employee_ids on
res.users being read as sudo.
The fix does work but was wrong because it gave access to the user's
public employee regardless of the active company_id
A domain was added to employee_ids to make force the security rules even
in sudo.

closes odoo/odoo#94558

Signed-off-by: Kevin Baptiste <kba@odoo.com>