Approval processes are always based on the people traveling. That means when booking a trip that requires approval, the trip is sent to the traveler's approver.
Let's take a look at some examples:
- Travis (the traveler) is approved by Alex (the approver)
- Bruce (the booker) is approved by Anna (the approver)
When Bruce is booking a trip for Travis, it will require approval from Alex.
Examples of how approval processes work
|Booker||Traveler||Approver||Ask for approval?||Notes|
|Bruce||Travis||Alex||Yes ✅||Approval request sent to Alex|
|Travis||Travis||Alex||Yes ✅||Approval request sent to Alex|
|Travis||Bruce||Anna||Yes ✅||Approval request is sent to Anna (even if Travis is an admin)|
|Alex||Travis||Alex||No ❌||No approval needed, since the Booker = Traveler's Approver|
|Alex||Alex||Alex||No ❌||No approval needed, since the Booker = Traveler's Approver|
This setup lets your company make sure that all approval requests are sent to the right person. In most cases, this is the traveler's line manager.
In case your current approval configuration is not based on the traveler, we recommend you to:
- Check your approval processes to make sure they are configured following the logic above, where the approvers are for the traveler. You can do it by editing each approval and verifying:
- Who is the approval process for? (travelers)
- Who should approve their trips? (approvers)
- Understand if the change of configuration requires extra implementation. For any help, you can always reach out to your account manager.
If your organization follows a line manager hierarchy, you may be interested in automating approval processes with your HR system.