Limits, troubleshooting & FAQ
Limits and constraints
| Constraint | Detail |
|---|---|
| An employee is not deleted | Terminate instead; history references them permanently |
| Leave belongs to the year of the start date | A request spanning New Year debits the old year in full |
| Pending days are held, not spent | They block a competing request but are not “taken” until approved |
| Payroll reads the stamp, not the leave | Deduction is decided at approval time and recorded on the request |
| Attendance devices must be registered and keyed | An unregistered device or a missing key is rejected — an unauthenticated punch is not accepted |
| Self-service reaches only the linked user | An employee with no user account gets nothing that requires a login |
Recruitment lives only under /hr/recruitment | There is one hiring pipeline, not one per app |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| An employee cannot log in | No linked user account, or it was deactivated | Settings → Users |
| A leave request found no approver | The employee has no manager set | Set the manager, or route the step to a role instead |
| The balance looks wrong after a rejection | It should not — pending is released on reject, cancel and termination alike | If it persists, report it; balance symmetry is an invariant |
| Leave over New Year came off the wrong year | It came off the start year, by design | Split it into two requests if each year should carry its own days |
| Payroll did not deduct unpaid leave | The deduction is stamped at approval; leave approved after the run was computed will not be in it | Recompute the run |
| Attendance shows nothing from a device | The device is not registered, or its key is missing | Register it and set the key |
| An employee sees company-wide HR data | They have hr:read, not just hr:own | These are separate doors — remove hr:read |
| Announcements do not appear for staff | They need announcements:read, which is not implied by hr:own | Grant it |
FAQ
Q: How many leave types can I configure? A: Unlimited. Each type (annual, sick, unpaid, compassionate, public holiday, or a custom type) has its own balance pool and accrual rule set in Leave Accrual Rules.
Q: Can leave approval require more than one approver? A: Yes. Leave Management supports multi-level approval chains — for example, direct manager then department head — configured in HR Settings.
Q: Where do I manage attendance and biometric devices? A: In the Time Tracking app, not HR. HR still shows employees their own attendance summary in Employee Service, and the same reporting line drives both apps, but schedules, overtime, and device registration moved to Time Tracking so there’s a single place for all time capture.
Q: What happens when an employee leaves? A: Mark them Resigned or Terminated. Their pending leave requests are cancelled, historical records are retained for audit, Self-Service access is revoked, and any unused-leave settlement is available for the final payroll run.
Q: Do managers only see their own team? A: If team-based data scope is enabled, managers see employees in their reporting line (driven by the Organization chart), while HR admins see everyone.
Q: Does AI ever hire, reject, or advance a candidate on its own? A: No. The Recruiter Copilot agent scores and ranks candidates and proposes actions (shortlist, schedule an interview, flag a stale application), but every proposal sits in a suggestion queue until a recruiter approves it.
Q: Can an employee submit a job requisition or does hiring start with a posting? A: Hiring starts with a requisition — an approved request for headcount tied to a department and position. A job posting can only be created against an approved requisition, which keeps hiring aligned with budget.
Q: What’s on the employee record besides basic profile info? A: Seventeen tabs: Overview, Personal, Work History, Education, Skills, Skill History, Training, Performance, Development Journey, Career, Contracts, Salary, Payroll Tax, Leave, Advances, Onboarding, Documents, and Notes — everything about one person on one record.