{{ __('Approval Hierarchy') }}

{{ __('Path') }}: {{ __('Workflow Settings') }}{{ __('Hierarchy Setup') }}{{ __('Approval Center') }}

{{ __('1) Workflow Settings (how chains are maintained)') }}
{{ __('Example') }} {{ __('Scope = Department-wise. Karim (Finance) applies Leave → Finance chain. Rahim (Program) applies Leave → Program chain. If Program has no rules and fallback includes Global → use company-wide Leave rules.') }}
{{ __('2) Add / Update Hierarchy Rule (what each field means)') }}
{{ __('Field') }}{{ __('Meaning') }}{{ __('Example') }}
{{ __('Request Type') }} {{ __('Which application uses this chain.') }} {{ __('Leave Application · Staff Separation · Staff Separation Reinstate') }}
{{ __('Department / Branch') }} {{ __('Empty = Global rule (fallback for all). Filled = only that dept/branch.') }} {{ __('Department = Finance') }}
{{ __('Stage label') }} {{ __('Display name of this approval step.') }} {{ __('Line manager / HR / Director') }}
{{ __('Level') }} {{ __('Order in the chain (1 first, then 2, …).') }} {{ __('1 → manager, 2 → HR') }}
{{ __('Approver type') }} {{ __('How the system picks the person.') }} {{ __('See below') }}
{{ __('3) Approver type') }}
{{ __('Example chain') }} {{ __('Leave · Finance · Level 1 = Direct supervisor · Level 2 = Fixed user (HR Admin) · Level 3 = Fixed user (ED). When Karim applies leave: first his supervisor, then HR Admin, then ED — all visible in Approval Center.') }}
{{ __('4) What happens after save') }}
  1. {{ __('Employee submits Leave / Loan / Separation / etc.') }}
  2. {{ __('System freezes the matching chain on that request.') }}
  3. {{ __('Approvers act in Approval Center level by level.') }}
  4. {{ __('Final approve updates the original record (leave approved, loan activated, …).') }}
{{ __('Policies (skip self-approval, remove duplicate approvers, skip inactive users) are set on Workflow Settings.') }}