Replies: 2 comments 1 reply
-
Why publishing in a general forum instead of OCA/sign? Anyway, that feature should go in a |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi. Interesting question ! A remark : i think it's maybe more global than sign feature. It could concern all mails sent to HR people. Not just d'oc to sign. Dont you think ? (I think about payrolls for exemple) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
In our projects we are using sign_oca integrated with HR, and we found a need that I’d like to discuss with the community:
Currently, when sending documents to employees for signature, the system usually takes the corporate email defined in the employee’s related user/partner record. However, in many cases we would like to use the employee’s private email (stored in the HR Employee form) instead of the corporate one, especially for legal or contractual documents that employees should be able to access outside their work accounts.
Add a configuration option at employee level (or in HR settings) to choose whether signing requests should be sent to the corporate email or to the private email.
Alternatively, allow sign_oca to detect and use the private email field of the employee model if configured.
Employment contracts or legal documents where it’s important that the employee can access them through their personal account, even if they leave the company or lose access to the corporate account.
Do you think this belongs in sign_oca itself or should it be handled by a separate HR-related module (e.g. hr_sign_private_email)?
Would you prefer a per-employee toggle (field in hr.employee) or a global HR configuration setting?
Thanks for your feedback!
Beta Was this translation helpful? Give feedback.
All reactions