Set Up the Hiring Module
Hiring works from rules an HR administrator sets once: who may do what, the job descriptions and pipelines a posting starts from, who approves, how long applicant data is kept, and how applications are scored. This walkthrough sets all of it up for one company, in the order the Settings list shows it, and ends with a company that can open its first posting.Before you start
You need access to Settings → Users & Access (roles) and the Hiring Settings permissions, and the company's departments, positions and job grades must already exist in Organization. The example used throughout:
- Demo Company will hire two Warehouse Associates for its Warehouse department, grade GS1 General Staff 1, paid up to 22,000.00 a month each.
- Hannah Reyes (an HR manager) approves postings, offers and manpower requests; Aaron Ramos and Ramon Manalo interview; the demo account plays HR.
- Applicants are kept 18 months, offers stay open 48 hours, and people can start on the 1st or the 15th of a month.
Reference for every screen: Hiring Settings. When the set-up is done, follow Run Hiring Day to Day with the same company.
- 1. Decide who may do what
- 2. Give each job grade a hiring budget rate
- 3. Build the job description library
- 4. Set up applicant fields and sourcing channels
- 5. Create the hiring pipeline
- 6. Set the pipeline defaults: stages, approval, start days and interviews
- 7. Set promotion, pre-employment items and medical classes
- 8. Set applicant data retention and the consent text
- 9. Check the hiring documents
- 10. Add a keyword dictionary for screening
- 11. Write an interview guide
- 12. Set the manpower request rules
- 13. Set up the talent pool
- 14. Decide what starts by itself
Open Settings → Users & Access → User Levels → Add. A user level is a named bundle of permissions; roles then carry the levels. Create one level per kind of person in Hiring.
| Person | Levels | What they can do |
|---|---|---|
| HR recruiter | Recruitment Create, Update, Publish; Interviews; Offers Create | Open the Hiring screens, create and publish postings, add applicants, schedule interviews, draft offers |
| Approver (Hannah Reyes) | Recruitment Approve/Reject; Offers Approve/Reject; Manpower request approve | Be named as approver of postings, offers and requests; cannot approve their own |
| Interviewer | Interviews | See and score the interviews they are on |
Every approver you name later (postings, offers, requests) must hold the matching approve permission, or Ante refuses to save the rule: “Every approver needs the approve offers permission”.
- 1The Medical results gate: who may see or record pre-employment medical results
- 2Add people: name the nurse, the doctor or the HR person who handles results
Medical results need one more step. Open HR → Settings → Access Gates, find Medical results and choose Add people. Only the people named there can see or record a result, even a role with every Hiring permission cannot.
- 1The Hiring branch: ticking it grants every Hiring permission below it
- 2Recruitment › Create: make job postings and add applicants
- 3Recruitment › Publish / Close: publish a posting and close it
- 4Interviews: schedule interviews and enter results
- 5Recruitment › Approve/Reject: left empty here, because approvers get their own level
A posting's salary budget comes from the job grade of its job description. Open HR → Settings → Organization, choose the Job Grades tab and edit grade GS1 (the Hiring salary permission is needed to see the field).
| GS1 hiring budget rate, per opening per month | 22,000.00 | |
|---|---|---|
| Openings on the posting | 2 | |
| Salary budget of the posting, per month | 22,000.00 × 2 | 44,000.00 |
Reference: Job Grades.
Open HR → Hiring → Settings → Job Descriptions. Every posting is built from a job description, so create one per role. Choose New Job Description.
Every save that changes the content keeps a numbered version. A posting keeps the version it was built from, and a job description that was ever posted cannot be deleted.
- 1Visible: whether the field appears on job descriptions
- 2Required: whether it must be filled
- 3Applicants: whether applicants see it on the careers page
- 1New Job Description: add a role to the library
- 2Library: the list of job descriptions
- 3Template: the fields every job description uses
Open Applicant Fields. These lists sit behind the standard questions (school, course, graduation year, home province, gender) a posting's application form can include.
- 1Add Channel: add one of your own
- 2A custom channel the company added
- 3Referral: can be renamed but not hidden, because its links credit the referring employee
Open Sourcing Channels. The built-in channels (company site, Facebook, LinkedIn, JobStreet, Indeed, school, referral, walk-in, other) are there; Add Channel creates your own, here Barangay job fair. A channel can be renamed and hidden from the picker; a hidden channel stays on its links and in reports. The list shows how many links use each.
- 1Schools: the list applicants pick their school from
- 2Courses: the list applicants pick their course from
- 3Gender: the options and the switch for asking it on forms
Open Hiring Pipelines. Each pipeline is a set of stages; a new posting takes a copy of the pipeline you pick, so changing a pipeline later never changes a posting that is already pending approval, published or closed. Choose New pipeline, name it Warehouse hiring and start from a copy of Fast track, then open it.
- 1Default for: Individual postings start from this pipeline
- 2Stage label: what applicants and HR see
- 3Open (days): how long the stage takes applications or work
- 4Review (days): extra days after the cutoff for HR to finish
- 5Open in Process Builder: the workflow kept behind the pipeline
Here the Exam stage is renamed Practical test, the Medical stage is removed and the stages read Application, Screening, Practical test, Interview, Offer.
| Application: open 7, review 0 | 7 days | |
|---|---|---|
| Screening: open 3, review 1 | 4 days | |
| Practical test: open 7, review 0 | 7 days | |
| Interview: open 5, review 1 | 6 days | |
| Offer: open 3, review 0 | 3 days | |
| Typical length of the pipeline | 7 + 4 + 7 + 6 + 3 | 27 days |
- 1New Pipeline: start from blank or copy one
- 2Our new Warehouse hiring pipeline: 5 stages, 27 days
- 3Show archived: lists archived pipelines, which can be restored
Open Pipeline Defaults. It holds what every new posting starts with. Changing a default never changes a posting that already exists, and each posting can change its own copy.
- 1Postings need approval before publishing: Off, All postings or By hiring type
- 2Approved by: a workflow, or the built-in levels
- 3Approval levels: any one approver on a level approves it; levels go in order
- 1Default Panel Method: how the interviewers’ scores combine
- 2Offer answer window (hours): how long an offer stays open
- 3Offer approval: offers need approval before sending, with their levels
| Hire-by date | Result |
|---|---|
| Thu 7 Jan 2027, the earliest the 27-day pipeline fits | Not allowed: the 7th is not a start day |
| Fri 15 Jan 2027, the next allowed day | Suggested in the dialog and accepted |
| Fri 1 Jan 2027 | Allowed, but too soon for the pipeline (the dialog says so) |
- 1A default stage: type, label and cost model
- 2Open (days)
- 3Review (days)
- 4Add Stage
Further down the same screen:
Hard-copy submission date is required in the built-in list, so a candidate cannot be promoted until HR records it. You will meet this in the day-to-day tutorial.
- 1Promotion needs a workflow: promote only through the chosen workflow
- 2Pre-employment requirements: items recorded before a candidate can be promoted
- 3Detailed application documents: files the detailed form asks for
Further down, under Applicant Data:
{months} is replaced with the retention months.| Her last activity (screened out) | 20 Nov 2026 | |
|---|---|---|
| Keep Unsuccessful Applicants | 18 months | |
| Due for removal, unless she is in the Talent Pool | 20 Nov 2026 + 18 months | 20 May 2028 |
- 1Keep Unsuccessful Applicants (Months): 6 to 120, here 18
- 2Consent Text: what applicants accept; {months} becomes 18
- 3Talent Pool: Review After (Months), 1 to 24
- 4Retention: who is past the period today (read-only)
Hiring Documents lists the printable documents a stage can produce (offer letter, interview sheet, exam result sheet, requirements checklist and more), with its number format and prefix, whether it is printed then scanned back, and how many pipeline stages use it. Open a row to preview it. The list is read-only; the company's numbering is set in Settings → Documents → Numbering.
- 1Offer letter: used by the Offer stage
- 2Interview sheet: used by interview stages
Open Keyword Dictionaries and choose New Dictionary. A dictionary scores a free-text answer during screening, so HR does not have to read every answer first.
The Warehouse dictionary has four concepts: Forklift (10), Inventory (8, also stock count, cycle count, stock-room), Picking (5) and Receiving (5).
| Answer: “Four years in a distribution centre: picking, inventory counts and forklift operation.” | ||
|---|---|---|
| Forklift found | 10 | |
| Inventory found (“inventory counts”) | 8 | |
| Picking found | 5 | |
| Receiving not found | 0 | |
| Keyword points for this answer | 10 + 8 + 5 | 23 |
- 1New Dictionary
- 2The Warehouse dictionary, ready to pick in a posting’s screening rules
- 1Name
- 2Role tag: groups dictionaries by job
- 3Concept: the word or idea to look for
- 4Weight: 1 to 100 points when found
- 5Synonyms: other words that count
Open Interview Guides and choose the add button. A guide is a reusable set of questions and scoring criteria; each interview stage copies one.
| Safety awareness: 10 × weight 2 | 20 | |
|---|---|---|
| Accuracy with counts: 10 × weight 1 | 10 | |
| Teamwork: 10 × weight 1 | 10 | |
| Maximum sheet total | 20 + 10 + 10 | 40 |
- 1New guide: questions and scoring criteria interviewers reuse
- 2The Warehouse associate interview guide
Open Manpower Requests. A department asks for people with a manpower request; these rules decide who approves it and whether a posting needs one.
| Rule | What happens |
|---|---|
| Off | Submitted as normal |
| Warn | Submitted, with a warning to HR |
| Required | Refused: link an approved manpower request first |
- 1Approved by: a workflow or the built-in levels
- 2Approval levels: who decides a request
- 3Postings need an approved manpower request: Off, Warn or Required
- 4Remind when an approved request has no posting after (days)
Open Talent Pool. People who agreed to be kept can be held here for a later opening. Saving needs the Talent Pool settings permission.
| Added to the pool | 20 Nov 2026 | |
|---|---|---|
| Keep records for | + 12 months | 20 Nov 2027 |
| Days left badge turns amber | − 30 days | 21 Oct 2027 |
- 1Keep records for (months): how long a new entry is kept
- 2Remind HR before expiry (days): when the Days left badge turns amber
- 3At expiry: Anonymise or Delete what Remove does
- 4Ask for consent again: required on renewal
- 5Invite message: the text Invite to apply starts from
Open Automatic Starts. Workflows can start by themselves, once per person, on a Hiring event.
The tutorial leaves both off: the example hires by hand.
- 1When an offer is accepted, start a workflow for the candidate
- 2When someone is promoted to employee, start a workflow for the new employee
What the set-up produces
| People: recruiter, approver, interviewers, medical gate | 3 levels + 1 gate | |
|---|---|---|
| GS1 budget × 2 openings | 22,000.00 × 2 | 44,000.00 per month |
| Job description + pipeline | Warehouse Associate · Warehouse hiring (27 days) | |
| Approvals | Postings, offers and requests: Hannah Reyes | |
| Applicant data kept | 18 months · pool 12 months | |
| Hires may start on | the 1st or the 15th |
The company can now raise its first manpower request and open its first posting.
Where to go next
- Run Hiring Day to Day — the same company hires two Warehouse Associates, from the request to the new employees.
- Hiring Settings — every section and field of this screen.
- Manpower Requests and New Job Posting — the screens these rules feed.