Overview
Recruitment covers the hiring pipeline end to end: job openings, a talent pool and candidate tracking, interview scheduling, offers, job requests (a department asking to hire), and the joining pipeline once an offer is accepted. On hire, a candidate becomes an HRMS employee record. Opening it needs a hiring view key (see Permissions below) and a department that allows Hiring.Where to find it
Core workflows
Post a job and assign a hiring manager
- Go to Recruitment → Job Openings → Post new job.
- Set Title, Department, Type, Status, Skills, and a real Hiring Manager — a workspace member picker, not free text.
- Fields beyond those (Experience, Application Deadline, Salary range, Location, Job Description, Publish-To) are present on the form but are not yet saved — see Known limitations below.
Move a candidate through the pipeline
- Candidates land in Talent Pool or Candidates (via the careers page or manual entry).
- Open a candidate’s detail page to move them through your pipeline stages, log interview feedback, and progress toward an Offer.
Schedule an interview
- Interviews (
/recruitment/interviews) is where interview slots are tracked. The Schedule Interview dialog itself has known data-entry gaps — see Known limitations below before relying on it for anything beyond a placeholder record.
Hire and onboard
- Accepting an Offer moves a candidate into Onboarding (the joining pipeline), and on completion creates the corresponding HRMS employee record.
Permissions
Two controls must both allow a member in. The member’s role must grant a hiring key, and the member’s department must allow Hiring. Workspace owners and admins are not limited by a department. The hiring roles are Recruiter, Hiring Manager, Interviewer and External Recruiter, assigned in Settings → Modules → Hiring → Team & roles. Opening the module. Any one of these seven view keys opens the Hiring dashboard:
Each section. A page or sidebar item opens only with a key for its own section, and a section
page also needs one of the seven view keys above, so a section key alone never opens Hiring. A
broader key covers a narrower one: a workspace key also opens a page that needs the assigned or own
key.
An Interviewer, for example, sees only the dashboard and Interviews, and gives feedback from the
interview itself. A section the member’s role allows but whose data is refused shows a “You don’t
have access” message, not an empty list.
Hiding Hiring from one member. A deny on a single key does not hide the module while the member
still holds another key from the list of seven. To hide Hiring from a member, deny all seven view
keys above, or remove the member’s hiring role. Denying
recruitment.job_postings.view.workspace
alone, for example, leaves an Interviewer or External Recruiter with their own interview or
applicant key, so Hiring still opens for them. Their data stays limited to their own scope.
Known limitations
- The Schedule Interview dialog’s form fields (Candidate, Position, Round, Date, Time, Mode, Meeting Link, Notes) are not wired to the form state — only workspace and status reach the API on submit. There is also no interviewer field yet (interviews can involve more than one person, so this needs a proper multi-person model, not a single field) — both are tracked as known gaps to fix, not silently accepted.
- The Post New Job dialog saves Title/Department/Type/Status/Skills/Hiring Manager, but Experience, Application Deadline, Salary range, Location, Job Description, and Publish-To are entered in the form and then silently dropped on submit — also a tracked known gap.