Leave approval workflows
Approvals that match how your organization actually works — manager first, admin when it matters, every decision logged.
Manager → admin, with one setting
Requests go to the employee's direct manager first. If your policy requires it, they then route to an admin for final sign-off. Employees without a manager route straight to an admin, and super-admins can approve or override at any stage.
Context before every decision
Approvers see the requested dates, the employee's current and projected balance, coverage warnings for the team, and the full request history — so they can decide in seconds without chasing details.
Auditable by design
Every submission, approval, rejection, and override is recorded with who did it and when. Bulk-approve a backlog, reject with a reason, or override a decision — it's all in the trail.
Frequently asked questions
Can Orvella require two levels of approval?
Yes. With a single setting, requests route to the manager first and then to an admin for final approval. You can also keep it single-level if that fits your team.
What happens if an employee has no manager?
Their requests route straight to an admin, so nothing gets stuck without an approver.
Are approval decisions logged for audit?
Yes. Every approval, rejection, and override is recorded with the actor and timestamp, and the full history is exportable.