Maintain the employee profile

What this achieves

The employee profile gathers everything Humavera holds about one person across a set of tabs. Keeping it current matters because every other module reads from it rather than holding its own copy.

Required role: Administrator. Managers can view their own reports.

Steps

1. Go to Employee Directory → All Employees.
2. Search by name or email, or filter by Status, Department, or Location.
3. Open the person.
4. Use the tabs to read or update each area.

The tabs

Option	Description
Overview	The core record — personal, contact, employment, and organizational details.
Skills & Competencies	What this person is credited with.
Learning	Their courses and paths.
Assessments	Assessments involving them.
Career	Career and development records.
Compensation	Salary, grade, allowances, and variable pay.
Documents	Files held against them.
Onboarding and Offboarding	Their checklists.
Activity	What has happened on this record.
History	Changes over time.

Which tabs appear depends on which sections your workspace has enabled and which modules your plan includes.

Masked fields and the reveal permission

Sensitive identifiers are stored encrypted and displayed masked, marked as encrypted on screen. Revealing one is a deliberate action rather than something that happens by opening the page.

Someone without the reveal permission is told they do not have it. That is a role setting, not a fault with the record.

Example: an HC Corp UK Ltd administrator can see that an identity document is held without reading it. Reading it is a separate action available only to those permitted.

Treat reveal as something you do when you need the value, not as a default view.

Employees maintain part of their own record

Employees can update their own contact details and similar personal fields. Fields with consequences — salary, department, manager, employment status — stay under administrator control, because changing them changes pay, reporting, and entitlement.

Example: James Whitfield can correct his own phone number after moving. He cannot change his own grade or who he reports to.

Editing versus the dedicated flows

Ordinary corrections are made by editing the record. Three changes have their own flows because they have consequences beyond the field:

Option	Description
Pay and contract changes	Effective-dated, with a grade band check.
Status changes	Dated, reasoned, and reviewed before confirming.
Offboarding	A checklist, not a deletion.

Use those rather than editing around them, or the history will not explain what happened.

History and activity

The History tab records changes over time and the Activity tab records what has happened on the record. Between them they answer what changed, when, and by whom — which is the question that arrives months later when a figure is disputed.

What happens next

An accurate record keeps everything downstream correct: payroll reads the salary and entity, leave reads the tenure and manager, learning reads the department, and the org chart reads the reporting line. Where a record is wrong, correcting it here is what fixes the symptom someone reported elsewhere.

Related

• Record a pay or contract change
• Change employee status or transfer
• Manage employee documents
• Setup Considerations: employee data