Keep employee records and profiles
Viewing and editing are separate permissions. Most people need to see a colleague’s desk details and nobody outside HR needs to change them.
Employees holds the employment record end to end: the profile, the onboarding of a starter, attendance and timesheets, leave and its balances, and the requests and notes that accumulate around a person. It is the most finely divided module in the suite — twenty-six permissions — because almost nothing in it should be visible to everyone.
The employment record, from onboarding to attendance — 26 permissions, the most finely divided module in the suite.
Viewing and editing are separate permissions. Most people need to see a colleague’s desk details and nobody outside HR needs to change them.
Onboarding is run as a process rather than remembered as a checklist in somebody’s head, which is what makes the second starter as complete as the first.
Corrections are permissioned separately from recording, and approval is the point at which a timesheet becomes something payroll may read. Devices are managed here too.
Requesting, deciding and setting balances are three different rights. Setting a balance is effectively granting time, so it belongs with whoever owns the policy, not whoever approves the day off.
The schedule is what attendance is measured against. Change one mid-period and every figure either side of the change means something different.
Notes about a person are permissioned apart from the rest of the record, deliberately. Read access to an employment record is not read access to what a manager wrote about somebody.
Written, published and made company-wide are separate steps, so drafting an announcement is not the same act as sending it to everybody.
The capability list this guide is written against, unabridged. Nothing above adds to it.
Employees on the Human Resources pageThe modules Employees hands work to, or takes it from. Most problems that look like one module are a handover between two.