What every module has in common

One employee record, two languages, and the same rules everywhere — from the first check-in to the final payslip.

Arabic and English, one build: Every page is rendered on the server in the reader's language and direction, so the first paint is already correct.
One employee record: Add someone once. Attendance, leave, payroll, reviews and documents all read the same row.
Roles that follow the org chart: A manager sees their own team. Salary stays with the people who are meant to see it.
An audit trail on every change: Who changed what, when, and what it was before — exportable for any period.
Approvals that end somewhere: Requests route by policy rather than by memory, and stop escalating once a decision is made.
Exports that open where you work: Any table leaves as XLSX or CSV, with the columns on screen and in the language you are reading.

Arabic is not a translation layer added at the end

The direction of the page, the shape of the type and the order of the columns are all decided before the first byte is sent.

lang and dir are set on the server, so nothing flips after the page loads.
Arabic has its own line heights and weights, never Latin metrics wearing a different font.
Numbers, dates and amounts stay left to right inside an Arabic sentence.

Layla HaddadSenior Accountant

Active

Six modules, one record between them. Each page goes further into the detail.

What each module covers
Module	What it covers
Employee Management	Profiles, contracts, documents and the reporting lines everything else reads.
Attendance	QR check-in, shifts, overtime hours and the nightly reconciliation.
Payroll	Salary components, advances, and payroll runs that keep a snapshot of what was approved.
Recruitment	Vacancies, candidate pipelines and the handover into an employee record.
Performance	KPI plans, review cycles and the scores that feed them.
Leave Management	Balances by tenure, holiday calendars and approvals that respect both.

Role-based access: Every screen and every field checks the signed-in role before it renders.
Audit logging: Each change is stored with its author, its timestamp and its previous value.
Encrypted in transit and at rest: Traffic runs over TLS, and stored data is encrypted on disk.
Single sign-on: Connect your existing identity provider and keep one set of joiners and leavers.

A demo runs against your departments, your grades and your leave rules — not a generic sandbox.