TAC HRTAC HR
Approval Workflow Setup Guide for Employee Requests
Practical guides

Approval Workflow Setup Guide for Employee Requests

Set who approves each request type and in what order: multi-step chains, auto-approval within limits, filing on behalf, request chat and the archive.

Last updated10 min read

An approval workflow is the chain of people who review a request and decide on it. You set one for each request type on the Approval Chains screen. TAC HR ships 37 ready request types and lets you add your own. Each type gets a route of one or more steps, in sequence or in parallel. This guide takes you from choosing approvers to the archive of closed requests. The admin web interface is in Arabic, so screen names are given in English.

Checklist before you start

  • The Employee Requests service is in your subscription.
  • Admin accounts for every approver. Approving on the web needs an admin account, not just a mobile account.
  • Direct managers are set in the employee files if you want a "direct manager" step.
  • A list of who approves each group: leaves, work time, finance, letters and documents, and career path.
  • The request types you want to hide from the app.

The ready types

The ready types fall into five groups:

GroupExamples
LeavesAnnual, sick, emergency, unpaid, maternity, paternity, Hajj, marriage, bereavement
Work timeExcuse, early leave, forgotten punch, lateness removal, overtime, business trip, shift or location change
FinanceAdvance, allowance, bonus, expense claim, IBAN change
Letters and documentsLetters, clearance, document renewal, data change
Career pathTransfer, promotion, training, resignation, device change

Steps

1. Add your own type

From Recent Requests click "New type". Enter the request name and its English name, and choose an automatic action on approval: no action, notify HR, or add a note to the employee file. Pick an icon and click "Save type". The type appears to your employees in the app. You manage types on the Request Types screen, reached from "New request type" or from Establishment Settings, then Excuses.

2. Decide what employees see in the app

In Establishment Settings open Mobile App and, in each group, select the requests an employee can submit. A type that is not selected does not appear in the request list.

3. Open the type's route

From Requests open Approval Chains. The board shows a card for each type with its steps and the number of pending requests, with "Edit" and "Reset". A type you have not edited follows the shared route.

4. Choose the approval mode

In the Approval Chains window pick "In sequence", where each group approves after the one before, or "In parallel", where all groups can approve at the same time.

5. Add the approvers

Under "Admins who approve or reject" click "Add approver" and choose one of three:

  • Admin group: everyone in it can decide.
  • Specific user: one named person.
  • Direct manager: resolved for each request from the requester's file. If that manager has no admin account, request supervisors in their scope pass the step.

In sequence mode the route ends with "Accept request" after the last step. Under "Admins who watch only" add observers, who view the request without acting. Click "Save". A route with no approver stops every request of that type, so the system refuses to save it.

If the route has pending requests, changing its structure would orphan them, so close them from the requests inbox first and then edit.

6. Turn on auto-approval within limits

On Request Types open "Auto-approval within limits" and click "Configure" next to the type. Turn on "Auto-approval within limits" and set "Maximum per request" and "Monthly limit per employee". A request inside both limits is approved instantly without reaching the approver. Anything beyond goes to the approver with a flag. The unit depends on the type: days for leaves and business trips, minutes for early leave, overtime and excuses, an amount for advances, allowances, bonuses and expenses, and a count for the rest.

Example: overtime with 120 minutes per request and 600 minutes per month. A 90-minute request is approved instantly. A 150-minute request exceeds the per-request limit and goes to the approver, and so does any request that would push the employee past 600 minutes in the month.

Auto-approval is off until you turn it on. Types such as resignation, IBAN change, device change, promotion, data change and clearance never enter this rule. Excuses also offer "App self-recording only".

7. File a request on behalf of an employee

In the employee file click "Request on behalf" at the top. The screen "Submit a request on behalf of" the employee opens. The request is recorded in the employee's name and follows their route, and its details show "Submitted on behalf". It suits staff without the app or who forgot to file.

8. Approve, delegate and discuss

Open the request from Recent Requests. The "Approval route" card shows the steps and progress. Write an optional note that shows to the employee, then click "Approve" or "Reject". Approval applies the request's effect immediately and cannot be undone. A traveling approver uses "Delegate decision to a colleague with approval authority": the delegate joins the step's approvers and is notified, and the original approver stays one.

  • Chat with the employee: the employee sees it in the request details on their phone and gets a notification for every message. Attachments are a PDF or an image up to 10 MB. "Close chat" makes it read-only and "Reopen" restores it.
  • Comments: an internal discussion between approvers, recorded in the request trail.
  • Cancel on behalf: "Cancel request" closes it as cancelled without deducting from the employee's balance, and approvers are notified.

9. Use the archive

Open the Requests Archive for requests that have finished: approved, rejected and cancelled. Anything still pending stays in Recent Requests.

Worked example: an annual leave through two levels

On Sunday 25 October 2026 an employee files an annual leave request from Sunday 1 November to Thursday 12 November 2026. The route for the «Annual» type is sequential with two steps: «Direct manager», then the «Human resources» group. The company set «Leave day counting» to «Working days» and the weekly rest to Friday and Saturday. The employee's annual entitlement is 21 days and none has been taken. The figures are an assumed example, each one is calculated by the engine's functions, and a permanent test recomputes them.

StageStatusWhat happens to the balance
Before filingNo request21.0 days available
After filingWaiting for the direct manager10 days are reserved, 11.0 available
After the manager approvesWaiting for HRThe reservation stays at 10, 11.0 available, and the second-stage approvers are notified
After the final approvalApprovedTaken becomes 10 and reserved zero, 11.0 available
If rejected or withdrawnRejected or withdrawnThe reservation is released and 21.0 is available again

The days: 1 to 12 November is twelve calendar days, including Friday 6 and Saturday 7 November. With «Working days» those two days are not deducted, so the request counts 10 days. If counting were «Calendar days» it would deduct 12.

Auto-approval: if a rule is set for leave with a maximum of 3 days per request and 5 days a month, this 10-day request exceeds the per-request limit, so it is not auto-approved and goes to the approver with the notice: "Not auto-approved: this request is 10 days and exceeds the per-request auto-approval limit (3 days). The decision stays with the approver." A two-day request is approved at once. A three-day request from an employee who has used 3 days this month exceeds the monthly limit: the limit is 5 and 2 days remain, so it goes to the approver.

Escalation when a request is late (off by default): "Approval routes" has an "Escalate late requests" switch for your establishment, and it stays off until you turn it on. In the route editor you give each approver a time limit in hours, from 1 to 2160, and an empty field means no escalation. The system checks pending requests every hour. When a step's limit passes with no decision, the request moves to the next approval step and its limit starts from the moment of the move. If there is no next step, as in a parallel route or on the last step, the HR admins whose scope covers the employee are notified and the request stays at its step. The approvers receive a notification, the escalation is written to the audit log, and request tracking shows "Escalated after the time limit". Each level is escalated once, and only requests that became pending after you turned the switch on are covered, so nothing that predates it is escalated. HR also sees the oldest pending request, in days, in the 07:00 morning digest. If the approver is away, you can still delegate their decision or edit the route.

Common mistakes

  • A route with no approver. It stops every request of the type, which is why saving is refused.
  • Editing a route with pending requests. Those requests are orphaned, so close them first.
  • An approver without an admin account. Approving on the web needs an admin account, not just a mobile account.
  • A monthly limit below the per-request limit. The system rejects it.
  • Leaving both limits empty. Set at least one limit, because auto-approval does not turn on without limits.
  • Approving a leave beyond the employee's balance. The system blocks it with a balance message and the request is not approved.

After setup

Pick the right route for each request with how to choose an approval route for each request, and tune excuses in the excuse policy. Approved advances and allowances then flow into the run as in the payroll setup guide, and excuses reach attendance as in the attendance setup guide. The other guides are in the guides hub.

Product link

The Employee Requests service in TAC HR covers leaves, advances, custody, letters and more with an approval route for each request type, auto-approval within limits, filing on behalf of the employee, a chat with attachments on every request, and an archive of closed requests. See Employee Requests.

Frequently asked questions

Can more than one person approve a request?

Yes. Add several groups in sequence, or in parallel when every approval is needed at the same time. A step can also require approval from everyone in it.

What if the approver is on leave?

They delegate their decision to a colleague with approval authority from the request page. The delegate joins the step and the request stays pending until one of them decides.

Does the employee learn why a request was rejected?

Yes. The note you write with the decision shows to the employee, and they can talk to you from the request details on their phone.

Can a type be approved automatically?

Yes, within limits you set. Some types never qualify because of their effect on money and identity.

Who sees the requests?

Anyone with the requests permission. An admin limited to a branch or department sees only that scope, and a direct manager who approves in a route opens an inbox of what awaits their decision.

Show us how you work, and we'll show you the difference.

In the demo we walk through a full day in your company: the morning punch, a request, the month's payroll, and the rep in the field, on data like yours.