Kellith

The employee record the rest of your HR stands on.

Attendance, leave, payroll and reporting are only as good as the record beneath them. Kellith keeps one — current, permissioned and shared by every module.

What it does

One person, one record

Every employee exists exactly once. Attendance marks, leave balances, payslips and activity all hang off the same profile, so nothing needs reconciling later.

Structure as data

Departments and designations are proper records with their own lifecycle — renamed once, reflected everywhere, never a dropdown of stale free text.

Permissioned to the field

Role-based access decides who sees salaries, who edits profiles and who merely looks people up. The directory is open exactly as far as you choose.

Ready for the rest of the platform

The directory ships with every Kellith configuration. Switch on attendance, leave or payroll later — they find the records already waiting.

Part of one system

Employee Directory doesn’t work alone.

04

Payroll

Payroll pays the people the directory knows.

Questions, answered

Can we import our existing employee data?

Yes. Straightforward rosters can be loaded during onboarding, and larger migrations from legacy systems or spreadsheets are handled as a custom engagement — reconciled, not just imported.

Who can see what in the directory?

Access is role-based and fine-grained. HR administrators, managers and employees each see exactly the fields their role permits — salary detail, for instance, is never visible by accident.

Is the directory a separate purchase?

No — it is the foundation of the platform and comes with every configuration. Other modules can be adopted one at a time on top of it.

Begin the conversation

See Kellith with your organisation’s names in it.

A thirty-minute walkthrough with your org structure, your leave policies and your payroll calendar — not a canned demo.

Already run on Kellith? Sign in to your console.