A new workspace has no leave types and no approval rules, so nobody can request leave until an HR administrator sets them up.
Who can do thisHR Administrator
A new workspace starts empty. HCM seeds no leave types and no approval rules. Until an HR administrator sets them up, employees have nothing to request, and any leave type that needs approval is refused with:
hcm.your-company.example/my-leaveSample data
Request leave
Leave type
Vacation
Start date
2026-11-23
End date
2026-11-27
Working days: 5· Balance after (estimate): 11.17 / 25 days - server is authoritative at submit time
Note (optional)
Anything your approver should know
Submit request
No approval route configured for leave requests.
PictureWhat an employee sees in a new workspace where no approval rule exists yet. The fix is on the HR side.
"No approval route configured for leave requests." means that no enabled approval rule matched the request. It is a setup gap, not a fault in the employee's request. Do these four things before you invite anyone.
1. Make sure there is an HR administrator
When a request has nobody else to go to, for example the employee has no manager, HCM sends it to the HR administrators. The workspace needs at least one person with the HCM Application Administrator role in the Tenant Portal. See Granting HCM access.
2. Create a leave type
Open SettingsLeave types and click Add leave type.
Enter a Name such as Vacation and a Code such as VAC.
Set Annual allowance (days). New types start at 20 days with Requires approval on.
For Danish holiday rules, choose Denmark - ferieloven under Policy template and click Apply.
Click Save.
3. Add an approval rule
Open the Approval rules tab and click Add rule.
In Approver role, type @manager:L1. That sends each request to the requester's direct manager.
Leave Mode on single. Leave the amounts and Dimensions empty, so the rule matches every leave request.
In Approver role, type @manager:L1 to route a step to the requester's direct manager, @manager:L2 for their skip-level manager, and so on (@manager:L{n} = n levels up the reporting line). The actual person is resolved from your org chart when the request is submitted. A plain role name (e.g. hcm_manager) routes to everyone holding that role instead.
In Approver role, type @manager:L1 to route a step to the requester's direct manager, @manager:L2 for their skip-level manager, and so on (@manager:L{n} = n levels up the reporting line). The actual person is resolved from your org chart when the request is submitted. A plain role name (e.g. hcm_manager) routes to everyone holding that role instead.
In Approver role, type @manager:L1 to route a step to the requester's direct manager, @manager:L2 for their skip-level manager, and so on (@manager:L{n} = n levels up the reporting line). The actual person is resolved from your org chart when the request is submitted. A plain role name (e.g. hcm_manager) routes to everyone holding that role instead.
Add rule
RoleAmount bandModeDimensionsTierStatus
@manager:L1- - -single0EnabledEditArchive
Add leave type
Name
Vacation
Code
VAC
Color
#5b48c7
Untracked (no annual allowance - never blocks on balance)
Annual allowance (days)
25
Requires approval
Policy template
Choose a country template…
Apply
Earned over the year
All 25 days are available from 1 January and must be used by 31 December. Nothing carries over.
CancelSave
Add leave type
Name
Vacation
Code
VAC
Color
#5b48c7
Untracked (no annual allowance - never blocks on balance)
Annual allowance (days)
25
Requires approval
Policy template
Denmark - ferieloven
Apply
Earned over the year
Days per year
25
Days arrive
Month by month
Holiday year starts
September
Day
1
Can be taken for (months)
16
Carryover cap (days)
5
Earns 2.08 days a month over 1 Sep 2026 - 31 Aug 2027. They can be taken until 31 Dec 2027 - 16 months from 1 Sep 2026. That runs 4 months past the next holiday year's start, so two holiday years overlap - an employee can hold days from both at once. Up to 5 unused days carry into the next holiday year; anything above that lapses. 2026 is only an example; the same pattern repeats every year.
Seeded from DK. Applying the generic template clears the stamp; hand-editing the accrual knobs above marks it "modified" in the list.
CancelSave
1/8Open Settings, Leave types. A new workspace has none. Click Add leave type.
Open Settings, Leave types. A new workspace has none. Click Add leave type.
Type the Name, Vacation, and the Code, VAC. New types start with 20 days and Requires approval on.
Choose Denmark - ferieloven under Policy template and click Apply. The accrual fields fill in: 25 days, from 1 September, takeable for 16 months, 5 days carry over.
Read the sentence under the fields, then click Save.
Vacation is in the list. Now open the Approval rules tab.
No approval rules defined yet. Click Add rule.
In Approver role, type @manager:L1: the requester's direct manager. Leave Mode on single and the amounts and dimensions empty, so the rule matches every request. Click Save rule.
The rule is Enabled. Employees can now request Vacation, and each request goes to their manager.
WalkthroughThe two things a new workspace needs before anyone can request leave: a leave type and an approval rule.
4. Check the basics
SettingsHolidays: the country is Denmark (DK). Turn on the customary days you give, such as Juleaftensdag. See Public holidays and company days.
SettingsDepartments: add your departments before you add people. See Departments.
Add employees with a manager each, and link their sign-in accounts. See Adding an employee.
Good to know
A leave type with Requires approval off needs no rule. Its requests are approved the moment they are sent.
A rule with @manager:L1 skips managers who have left or have no sign-in account. If nobody suitable is found, the step goes to the HR administrators.
Approval rules are matched on the number of working days and, if you set them, on leave type and department. A rule with empty fields matches everything. See Approval rules and routing to managers.
HCM sends no email. Tell your managers to check Approvals.