Assess
Map your current approval processes, hierarchies, thresholds, and the channels your teams use.
Automate multi-level approvals with configurable routing, full audit trails, and one-click actions in Microsoft Teams.

Manual and email-based approval chains slow businesses down. Teams lose track of who needs to approve a request next, hierarchies are hard-coded and difficult to change as thresholds or request types evolve, and decisions and comments are scattered across inboxes with little traceability. Approvers often have to log into a separate system just to act, which delays turnaround further.
LevelShift’s Approval Workflow Framework replaces fragmented approval processes with one configurable engine. Requests are routed automatically by cost or request type, every decision is recorded, and approvers can act from wherever they work: Model-Driven Apps, Power Pages, or Microsoft Teams. Changing an approval hierarchy becomes a configuration update, not a redevelopment effort.
Route requests by cost band (less than, greater than, between, or equal to) or by request type, with sequences defined in configuration rather than code.
Easy Process Changes:
Update approval hierarchies, thresholds, and routing sequences through configuration without modifying the underlying workflow.
Send rejected requests back to the requestor or to any previous approver, instead of ending the process outright.
Simplified Exception Resolution:
Enable requests to be corrected, reviewed, and resubmitted within the existing approval flow rather than restarting the process.
Capture every action, approver, and comment in a dedicated history table for full traceability.
Full Auditability:
Maintain a timestamped record of approval decisions, rejections, approvers, and comments to support compliance and reviews.
Requestors and approvers see the current approver and request status at a glance.
Greater Transparency:
Give stakeholders visibility into request progress and pending actions, reducing follow-ups and status chasing.
Approvers receive notifications in Teams and can approve or reject with comments without leaving the conversation.
Faster Turnaround:
Reduce delays between approval stages by allowing approvers to act directly within Teams.
One engine serves internal users in Model-Driven Apps and external users through Power Pages.
Consistent Process:
Enforce the same approval logic across internal applications and external portals through a shared approval engine.
A requestor creates a request in the Model-Driven App or the Power Pages portal and submits it for approval.
The framework matches the request's cost or type against the configured approval sequence and notifies the first approver.
Approvers approve or reject with comments from the app, the portal, or Microsoft Teams. Approved requests move to the next level, and rejected requests return to the requestor or a prior approver.
Once the final approver signs off, the request is marked complete, with a full history of every decision.
A requestor creates a request in the Model-Driven App or the Power Pages portal and submits it for approval.
The framework matches the request's cost or type against the configured approval sequence and notifies the first approver.
Approvers approve or reject with comments from the app, the portal, or Microsoft Teams. Approved requests move to the next level, and rejected requests return to the requestor or a prior approver.
Once the final approver signs off, the request is marked complete, with a full history of every decision.
Map your current approval processes, hierarchies, thresholds, and the channels your teams use.
Import the solution into your environment and connect it to your target tables, such as procurement or requests.
Set up approval sequences by cost band or request type, and add status and approval components to your forms.
Enable the framework on Power Pages for external users and in Microsoft Teams for in-context approvals.
Test approval paths end to end, train administrators and users, and provide ongoing support.