- 23 Feb 2018, 13:38
#3583
Additional note to protecting instances in DB:
Lot of DB tables have field 'owner', that can be linked to recruiter (this is used to in filter 'show only my candidates').
We had an idea to extend this functionality for similar purpose as is in this thread.
* Recruiter is owner of candidate.
* Hiring manager is owner of job order. Hiring manager can see only candidates, that are in pipeline of job order (to review candidate if fits to job order).
* Only recruiter can assign candidate to job order pipeline.
This was not implemented because there were more advanced requirements for this, for example management of candidates if recruiter is ill, to invite managers to review process, ... so above was not enough for this requirement.
But if anyone can contribute with such code, I think it would be useful and doesn't require (I expect) change of DB schema. Implementation can be done conditional way, that is to be able to switch required checks on or off.
Sveto
Lot of DB tables have field 'owner', that can be linked to recruiter (this is used to in filter 'show only my candidates').
We had an idea to extend this functionality for similar purpose as is in this thread.
* Recruiter is owner of candidate.
* Hiring manager is owner of job order. Hiring manager can see only candidates, that are in pipeline of job order (to review candidate if fits to job order).
* Only recruiter can assign candidate to job order pipeline.
This was not implemented because there were more advanced requirements for this, for example management of candidates if recruiter is ill, to invite managers to review process, ... so above was not enough for this requirement.
But if anyone can contribute with such code, I think it would be useful and doesn't require (I expect) change of DB schema. Implementation can be done conditional way, that is to be able to switch required checks on or off.
Sveto