Entities with their own regimes
Mainland, free zone, DIFC and ADGM entities coexisting, each resolving its own payroll, leave and end-of-service rules.
By company size
Enterprise & multi-entity
Groups running several entities across mainland, free zone, DIFC and ADGM, with thousands of employees, a procurement process and an internal audit function.
At group scale, the difficulty is no longer any single HR process — it's that you are running several of each, under different regimes, and someone has to be able to answer a question about all of them at once without a reconciliation project.
KLEDHR models the group as it actually exists: entities with their own jurisdictions, policies and approval chains, under one org record, one permission model and one audit trail.
Permissions at group scale
Roles scoped by entity, department, grade or reporting line, with reads on sensitive fields logged as well as writes.
Isolation & residency
Per-tenant database isolation with every record held in-country on Azure UAE North — the first two questions in every procurement pack.
Consolidated reporting
Group, entity and jurisdiction as dimensions, so one report answers the board question and the local one.
Governed AI
Audit logging, cost caps and confirmation before any data-changing action — the controls that let AI through an internal audit review.
Migration in stages
Entity by entity, with parallel payroll cycles, rather than a group-wide cutover nobody can roll back.
What procurement asks first
Enterprise selection is decided as much by the security review as by the demo. The answers are deliberately boring: the data is in the UAE, tenants are isolated at the database level, access is logged, and the AI cannot act without confirmation.
- UAE data residency on Azure UAE North, stated plainly and evidenced.
- Per-tenant database isolation rather than row-level separation.
- SSO, role scoping and leaver-driven access removal.
- An architecture pack covering residency, isolation, AI governance and retention.
Running several regimes at once
A group with mainland, free-zone and financial-free-zone entities is running distinct end-of-service arrangements simultaneously. They should not share a code path, and the product should never quietly apply one to the other.
- End-of-service treatment resolved from the employing entity.
- Transfers between regimes handled explicitly, with the effect made visible.
- Policy, contract templates and document formats held per jurisdiction.
- Reporting per regime or consolidated, from the same source.
Questions we get asked
- Can we get the architecture pack before a demo?
- Yes. Ask through the contact form and we'll send the residency, isolation, SSO and AI-governance documentation directly.
- How do you handle a phased rollout?
- Entity by entity, each with a parallel payroll cycle before cutover. Group reporting works across migrated and unmigrated entities during the transition.
See KLEDHR on your own payroll month
A 30-minute walkthrough on a tenant we spin up for the call — bring your trickiest gratuity or WPS case.
Book a demo