Inside the service
A request starts with the employee and ends with a written decision, and between the two stand three checkpoints your company controls: the balance, checked and reserved before anyone sees the request; the route, which decides who approves, who watches, and in what order; and the auto-approval rule, which shortens the path for small, recurring requests. Take a food distribution company with four warehouses in Riyadh, Qassim and Dammam and about 180 employees. A driver at the Qassim warehouse asks for two days of annual leave from his phone. He sees his balance before sending, knows afterwards whose desk the request is waiting on, and receives the decision as a notification.
01
The approval route follows the request type
Each request type in your company has its own route, edited on the approval routes screen. Approvers come from three sources: an admin group, a specific user, or the employee's direct manager, resolved from the requester's file at decision time. You then choose whether they approve in sequence, one after another, or in parallel at the same time, and each group shows its member count. When a step has no approver, such as an employee whose manager has no admin account, the request supervisors in that scope move it on, so nothing waits in silence. You add watchers who see the request without acting on it, such as the payroll accountant on leave requests. A route cannot be saved without an approver, and a route with pending requests cannot be restructured until they are settled. An approver can delegate the decision to a colleague who holds approval rights, and the request stays pending until one of them decides.
02
The leave balance is checked before approval
Annual leave is 21 days by default and rises to 30 days after 60 months of service, and in the year an employee crosses that threshold the entitlement is prorated by days. On the leave settings screen your company sets yearly or monthly accrual, the service period before the balance accrues and before it can be used, and whether days are counted as calendar days or as working days that skip the weekly rest day and public holidays. At filing, a pending request reserves its days, so two requests cannot draw on a balance that covers only one, two leaves cannot be accepted on the same day, and a leave that spans two years is split between them. At approval the check runs again on what was actually deducted, so the balance never goes negative, whatever order the approvals come in.
03
Auto-approval with limits your company writes
The request types screen has an auto-approval-within-limits table, and each type has its own unit: days for leave, minutes for permissions and early departures, an amount for loans and allowances, and a count for everything else. The rule is off for every type until you turn it on. Suppose the warehouses set annual leave to a limit of two days per request and four days a month. The driver asked for two days and they were approved at once with no approver, then one day, also approved, then two more days in the same month, with three days used and one day left. The request is not refused: it goes to the approver as usual with a note stating the limit, the days used and the days left. Usage counts approved requests only, and seven sensitive types never enter the rule, among them promotion, IBAN updates and resignation.
04
Leave types, requests and letters
Every company is seeded with nine leave types whose values you can change: annual, sick at one hundred and twenty days, emergency, unpaid, maternity at eighty-four days for women, paternity at three days for men, Hajj, marriage and bereavement. Each type has its days per year, its pay, its restriction and a maximum per request, and a disabled type accepts no new requests while its earlier balances stay as they are. Next to leave sit programmed administrative requests with a real effect, such as data changes, transfers between departments, resignation and the general request. Your company creates its own types with Arabic and English names and a category, and they appear to your employees in the app. The employment letter, the salary letter and the experience certificate are generated as a file after approval, saved to the employee's documents, and announced on the phone.
05
Employee relations with a written trail
In complaints, confidentiality is enforced in the data layer itself, so the author of a confidential complaint never appears in a report, an export or a notification. The response deadline runs from the moment of filing, and anything past it is escalated to the system administrator once. In violations, a daily engine reads lateness and absence events every morning and moves the employee one step up the ladder, from a note of attention to a first and then a second warning. Your company chooses whether the action is issued or proposed for review, and referral for investigation is never issued automatically. The employee acknowledges a warning from the phone, an acknowledgment of receipt rather than agreement, and can object within a window counted in working days from the acknowledgment. Alongside sit announcements and surveys, the community feed, and the custody items employees confirm they received.