Human Resources holds everything about the people who work here: who they are, when they work, what they are paid, how they are doing, and what they have agreed to.
Two Audiences, One Area
More than anywhere else in the platform, this area serves two different people.
Every employee uses a handful of surfaces regularly - clocking in, booking leave, reading a payslip, completing training, acknowledging a policy. Those articles are written for you and assume no admin access.
The HR team uses everything else - configuring leave, running payroll, managing records, running review cycles.
If you are looking for how to book leave, you want the first group. If you are looking for how to define what leave exists, the second.
What It Covers
| Area | Surfaces |
|---|---|
| Today | Dashboard, My Team, My Profile, HR Tasks, HR Alerts |
| Talent | Directory, Careers, Training, Engagement |
| Teams | All Teams, Staff Roster, Reporting |
| Compensation | Payroll, Session Reports, Integrations |
| Governance | Policy Studio, Documentation |
| Workflows | Boards, Inbox |
| Insights | Reports and Analytics |
The Thing To Understand First
The employee record is the identity the platform uses everywhere. Deal owners, approvers, task assignees, document signatories - all of them are employee records, not login accounts.
Two consequences: someone can exist as an employee before they ever sign in, and a login without an employee record cannot be assigned work. Most "why can this person not be assigned anything" questions resolve to this. See The Employee Record.
Everything Depends On The Hub
A hub is a legal entity, and Human Resources reads it constantly:
- The working week and business hours decide what counts as late
- Public holidays decide what counts as a working day
- The payroll profile sets tax, deductions, gratuity and the cut-off
- Leave types can differ per hub, because statutory leave is jurisdictional
A hub configured wrongly produces wrong attendance for everyone in it, every day. It is the highest-leverage setting in the module and the most common root cause. See Holidays and the Working Week.
Setting Up, In Order
- Hubs, with their working week, holidays and payroll profile.
- Departments and roles, so people have somewhere to sit and something they can do.
- Leave types, with allowances and eligibility.
- Employees, with compensation records.
- Policies, published to their audiences.
- Performance - the KPI library, then a review cycle.
- Payroll, last, because it reads all of the above.
Caution
The most common sequencing error is creating employees before the hub's payroll profile exists. The person appears everywhere, works, and then produces no payslip - discovered on payroll day. See Onboarding Someone.
Where Things Are Not
- Roles and permissions are in Settings, not here. Human Resources says who someone is; Settings says what they can do.
- Expenses are in Finance.
- Your own theme, mailbox and notifications are in your account settings.
Common Questions
Who can see salaries? Only roles granted it. Seeing the directory and seeing compensation are separate permissions, and the sensitive fields are encrypted at rest. See The Employee Record.
Can employees see each other's records? The directory shows names, departments and roles. Personal data, compensation and documents are separately permissioned.
Does this handle contractors? Employment type is on the record. How you treat contractors for payroll and leave is your policy.
Where do I start? An employee: Clocking In and Out and Booking Leave. An admin setting up: Holidays and the Working Week, then Leave Types and Allowances.
Did this answer your question?
No, ask a person