Default approval is simple but powerful: each leave request will be sent to the user's manager (as previously assigned or chosen) with key information including the date(s), type of leave, current balance, and other team members already on leave.
To graduate from the default, visit approval settings on the dashboard to specify where approvals are routed, how many levels of approval you'd like, and whether each step of notification requires approval or simply fyi notice. These settings are particularly valuable for organizations with a central administrator OR large organizations that want additional approval controls.
Here's how to navigate the page:
- Approvals versus Notifications
- The Approvals flow governs all types of leave that require approval, while the Notifications flow governs types of leave that are auto-approved (require no approval).
- However, note that within the approval flow, each additional level can be set as fyi-only, so you may use the approvals flow to configure multiple tiers of notifications rather than extending the approval process.
- Levels
- Levels must be turned "on" using the toggle to activate
- Each level represents a contingent subsequent step, and only occurs once the prior level has been resolved. For approvals, this means that additional approvals are only sent after the prior approve has been complete, so no simultaneous approvals are possible.
- Recipients
- Manager: The default recipient is always "manager" and always refers to the prior level. Level 1 manager will always be the manager of the requesting users, and level 2 manager will be the manager of the level 1 approver, and so on up the hierarchy.
- Custom: If you'd like a single specific users to be notified or approve, select the custom dropdown. This allows only one user per level, and is typically used to route approvals/fyis to a central admin or department lead, like HR, IT, or Finance.
- Tip:
Give this a try & let us know if you face any challenges setting these up by reaching out to our support team.