A clear route to
your workforce records.

After organisational onboarding and live access activation, an employee journey can provide assigned payslips, relevant leave balances and requests, insurance information and authorised employment-service cases. The record should identify the payroll period, approved entitlement or case status so the employee can distinguish a pending request from a completed transaction. A payslip is read with the payment credit and bank or agent result; it is not itself proof that a salary reached the account.

To raise a payroll concern, the employee should quote the pay period, affected item and case reference through the approved channel, without sharing passwords or unnecessary bank records. Leave requests go to the designated approver and become confirmed only after the required decision. Insurance e-card access depends on the connected insurer or benefits record and policy validity; an on-screen document must not be assumed to extend expired cover.

Workers retain their own passports and official documents. The planned service category is personal-document assistance, including tracking the prompt return of an original temporarily provided for an authorised transaction; it is not a passport-custody or permission-to-withdraw service. Identity, bank and contact changes require the authorised verification process. Sensitive employment and medical information should be visible only to the appropriate employee and authorised service owner.

A client role can be configured to review only the assignments, locations and records authorised for that account. Typical workstreams include attendance and overtime approval, mobilisation status, roster changes, monthly billing inputs and service actions. The user sees the period, version, exception and approval state rather than a single unqualified dashboard total.

Timesheet review should confirm the actual person, authorised hours, shift, absence and approval basis. Biometric attendance, if implemented, requires a lawful and proportionate data design, reliable interfaces, exception correction and restricted access. A biometric event is not automatically an authorised overtime instruction. Rejected or disputed records need a reason and owner so payroll and billing can reconcile differences without suppressing undisputed employee pay.

For billing, compare the contracted rate and approved headcount or hours with joiners, leavers, chargeable benefits, adjustments and the purchase-order reference. A client approval does not authorise changing employment terms, disciplinary status or a statutory entitlement outside the employing entity’s process. The mobilisation view should distinguish selected, authorised, site-ready and deployed personnel. Any roster export or supporting document must follow the agreed confidentiality and retention controls.

Internal roles can be designed around recruitment, employee administration, PRO, payroll, account management and welfare responsibilities. Recruitment users maintain mandate, candidate permission, assessment and offer status; operations users manage readiness and handover evidence; authorised PRO users track work permits, residence and Emirates ID dependencies. Access should follow the task and entity rather than grant all employee information to every internal user.

Payroll preparation, checking and final release require separated responsibilities. Changes to bank details, salary, employee status or permissions need an approved instruction, verification and a reviewable history. The control design prevents one user from creating an employee, changing the bank data and releasing the same payment without independent oversight. Authority response records and approval evidence are retained against the case, with sensitive files kept out of general client views.

Account governance follows open dependencies, client decisions, workforce changes, welfare cases and corrective actions. Reports should distinguish source data from reviewed conclusions and record the effective date of a roster or payroll result. Information-security and legal incidents use their protected escalation route. The live system must enforce permissions server-side; choosing an Internal Staff tab cannot grant internal authority.