In the current Interview doctype in Frappe HR, the Interviewers field is linked to the User doctype.
From a business and HR workflow perspective, interviewers are typically employees within the organization, and the system already maintains an Employee doctype that holds complete HR-related data for each staff member.
Linking interviewers directly to User accounts works for access control, but it also bypasses the established HR entity (Employee) and may cause:
- Redundant data mapping between User and Employee.
- Inconsistent HR reporting (e.g., if an interviewer is also an employee, data must be cross-referenced manually).
- Potential mismatch in cases where a User account exists but no Employee record is linked.
From an HR process standpoint, it would feel more natural to assign interviewers as Employees, since:
- Every employee who can interview should already have an Employee record.
- Employee records provide richer context (designation, department, employment status) useful in interview reports.
- Linking to Employee can still allow backtracking to User for permissions, while keeping HR data consistent.
*The Employee doctype also contains skill sets, experience, and profile information, which can be leveraged to evaluate the effectiveness of interview sessions and match interviewers’ expertise to specific job roles.
Questions for clarification: - Could you share the reasoning behind designing the Interviewers field to link directly to the User doctype rather than the existing Employee doctype, given that interviewers are typically employees in a real HR workflow?
- Are there any plans or considerations to revise this structure in the future—perhaps by linking to Employee for richer HR context while still maintaining User-based permission control?