Skip to content

Guide for the HR administrator

An administrator can reach almost everything in Humavera, which makes it hard to know where the actual work lives. This is a signpost to the parts you will use, sorted by how often you use them.

The employee record is the spine of the product, so most daily work is there: creating employees, maintaining profiles, handling documents, and recording status changes and transfers.

Alongside it, your approvals inbox carries whatever the workflows have routed to you, and the activity feed shows what changed in the workspace and who changed it.

Payroll is the fixed point in the calendar. The monthly payroll cycle walks the whole sequence, including the second-administrator approval a run cannot skip.

Around it sit the things that feed pay: leave balance adjustments, attendance approval where you pay on hours, and payroll reports at the end.

Joining runs through Hire to first payslip, and the step that catches people out is converting an accepted offer into an employee record, which does not happen on its own.

Leaving runs the other way: offboard a leaver and, where pay is owed, run a final settlement.

These are campaigns rather than tasks, and each has a guide or a considerations page worth reading before you start:

Disciplinary holds cases and the actions recorded against them, and Setup Considerations: disciplinary policy is the page to read before your first case rather than during it.

For pay that was wrong after a run was finalised, the routes are an off-cycle run or a correction in the next period — Setup Considerations: corrections covers choosing between them.

You hold the workspace itself: users and access, roles, security policy, notifications, and your plan and subscription.

You also own the structure everything else reads from — the organisation and its job architecture — and the approval routes that decide who signs off what.

If the workspace is new, work through Your first month as an administrator before anything here. If it is running, the useful habit is to read a section’s Setup Considerations page before its task pages: that is where the decisions you cannot cheaply undo are set out.