Approval flow case studies

Jo Ngan

25 October 2024 15:45

This article is dedicated to the different scenarios you may come across when using Approval flows and Approval thresholds:

Scenario: A team member creates an application that doesn't have any associated budget or payment method requirements.
Approval Flows: Since the application has no financial impact, it is set up to be created automatically, bypassing all approval steps.

Scenario: An application is created by a Team Manager or Admin.
Approval Flow: The application will bypass the first approval.
If Dual Approval is turned on: The application goes directly to the second-level approver for approval.

Scenario: An application is created by the second-level approver, and the request triggers both approval flows.
Approval Flows: Because the application creator is already at the second approval level, both the first and second approval stages are bypassed.

Scenario: Approval threshold is set for both Approval flow and Dual Approval flows, and the second-level approver creates an application with a budget that falls between the first and second approval threshold, and in turn, triggers only the first approval.
Approval Flow: If the approval threshold dictates that only a first-level approval is needed, the application will be sent to Team managers and Admins for approval, adhering to the defined threshold requirements.; The user being the second-level approver is irrelevant in this case, since second approval is not triggered.
Example: If Jo, the second-level approver, creates an application with a budget of £150, based on the Approval threshold setup, only the first approval is triggered.; The request will be sent to Admins and Team managers for approval, even though Jo is the second-level approver.