KAMI for administrators
What KAMI gives you as an administrator, the order to set it up in, and the order to learn it in. This is a map — every area below has its own article, and trying to read all of them before starting is the slowest possible route.
Where: the sidebar, plus Settings in each module You need: administrator rights
What you actually get
One record of employment. Profiles, contracts, documents, org structure, disciplinary history and career progression in one place, rather than in a folder system that only works while one person remembers it.
Payroll that is driven by the record instead of retyped from it. Attendance feeds timekeeping, timekeeping feeds payslips, and approved changes feed the next run. Most of the value in KAMI, and most of the risk, lives in that chain.
Configuration instead of policy documents. Leave types, approval routes, expense limits, overtime rules and validation checks are enforced by the system rather than described in a PDF nobody reads.
Evidence. Audit trails, reports and stamped approvals. When someone asks why an employee was paid what they were paid, the answer is retrievable rather than reconstructed.
The one thing to understand before you configure anything
Settings feed payroll, and most of them feed it silently.
An overtime window, a holiday rule, a leave type's accrual, a rounding setting — each looks like a small administrative choice on the screen where you set it, and each produces a wrong payslip for everybody at once when it is wrong. There is no preview that tells you a setting was a bad idea.
⚠️ Change payroll-affecting settings between pay runs, never during one, and check the next payslip yourself before assuming the change did what you intended.
The order to set it up
Each step depends on the one before it, and doing them out of order creates rework rather than errors — which is worse, because rework is invisible until you hit it.
| Step | Why it is here | |
|---|---|---|
| 1 | Company and subsidiary details | Everything else attaches to a company |
| 2 | Organisation structure | Branches, departments, positions — before anyone is added |
| 3 | User rights and access control | Decide who sees what before there is anything to see |
| 4 | Approval chains | Requests need somewhere to go |
| 5 | Module settings | Attendance, payroll, leave and expenses — the rules themselves |
| 6 | Adding and onboarding employees | People last, once the structure exists to put them in |
Adding people first is the common mistake. It works, and then every profile has to be revisited once the structure they should have been assigned to finally exists.
The Onboarding Wizard walks new companies through much of this. Use it if you are starting from nothing.
The order to learn it
Setting KAMI up and understanding it are different jobs. Learn in this order:
| Learn | When | |
|---|---|---|
| 1 | My Team for administrators | First — the module you will live in |
| 2 | User rights and access control | First week; it explains most "why can't they see it" questions |
| 3 | Getting started with Attendance | Before the first full week of check-ins |
| 4 | Getting started with Payroll | Well before the first pay run |
| 5 | How timekeeping is calculated | Before anyone queries a payslip |
| 6 | How wages are calculated | The same week as step 5 |
| 7 | The module you activate next | Benefits, Expenses, Performance, Learning, Invoicing |
Steps 5 and 6 are the two that turn you from someone who runs payroll into someone who can explain it. Almost every payslip dispute is answered by one of them.
Where the modules sit
Each has a getting-started article that maps it; none of them need reading until you activate the module.
| Module | Start at |
|---|---|
| My Team | My Team for administrators |
| Attendance | Getting started with Attendance |
| Payroll | Getting started with Payroll |
| Benefits | Getting started with Benefits |
| Expenses | Getting started with Expenses |
| Performance | Performance for administrators |
| Learning | Getting started with the LMS |
| Invoicing | Getting started with Invoicing |
| Tasks | Getting started with KAMI Tasks |
Modules are switched on per company — see Module activation and two-factor authentication.
The tools that save the most time
These are the ones administrators discover late and wish they had found early:
| Tool | Use it for |
|---|---|
| Bulk data import and export | Getting existing employee data in without retyping |
| Profile Manager | Changing a field across many employees at once |
| Bulk Assignments | Applying schedules, approvers and policies to groups |
| Profile Automations | Making routine profile changes happen without you |
| Missing Data report | Finding the gaps before payroll does |
| Audit Trail report | Answering "who changed this, and when" |
Run the Missing Data report before your first payroll, not after it.
What Happens Next
- Structure and rights changes take effect immediately and apply to everyone in scope.
- Payroll-affecting settings apply to the next calculation, not retrospectively — existing payslips are unchanged until recalculated.
- Approved attendance and leave feed timekeeping, which feeds the next payroll run.
- Every configuration change is recorded and attributable to you.
Tips
- Set up structure before people. The alternative is revisiting every profile.
- Change payroll settings between runs and verify on the next payslip. A wrong rule is wrong for everybody simultaneously.
- Give the narrowest rights that work. Widening access later is easy; discovering that everyone could see salaries is not.
- Run the Missing Data report on a schedule. It is the cheapest way to find the problems that stop a payroll run.
- Use the bulk tools before doing anything a hundred times. Almost every repetitive administrative job in KAMI has a bulk equivalent.
- Learn timekeeping and wage calculation properly. They answer most of the questions you will be asked, and guessing at them in front of an employee is expensive.
Troubleshooting / FAQ
Q: Where do I start with a brand new company? Company details, then organisation structure, then rights, then approvals, then module settings, then people. The Onboarding Wizard covers much of it.
Q: Someone cannot see a page they should have. Rights, or the module is not activated. See User rights and access control.
Q: A payslip is wrong for everyone. That is a settings problem rather than a data problem. Check the rule that produced the wrong line before correcting payslips individually.
Q: I changed a setting and nothing happened to existing payslips. Payroll settings apply to the next calculation. Existing payslips are unchanged until recalculated.
Q: Can I import our existing employee data? Yes — see Bulk data import and export.
Q: Who changed this record? The Audit Trail report.