The quick answer
In a configured ZoneApprovals workflow, an authorized super approver can act on another employee’s remaining approval step. Save the applicable employee configuration, return to the purchase order, select Approve, enter the required reason, and verify Approval Status, the original Approver, Overruled By, and Approval Reason.
Approving your own step does not approve every step on the order. This example follows PO7624 for Harbor Safety Supply: Alex Morgan completes an assigned step, then uses the configured override capability on Jordan Reed’s remaining step. Person and operating-company names are fictional example data. The screenshots show a configured simulation; this override was not exercised in the inspected production account.
Before you start
This procedure uses the third-party ZoneApprovals SuiteApp, an existing approval matrix, and authority under your organization’s approval policy. It does not demonstrate native SuiteApprovals or SuiteFlow approval routing.
The demonstrated form uses Approvals, Super Approver Checkbox, and Approve. Other SuiteApp versions, roles, and forms may show Zone Approvals, Super Approver, or different override actions. Default Administrator override may already be available in some configurations; the checkbox is not a universal requirement for every administrator. Permission to edit an employee does not establish permission to bypass your organization’s approval policy.
01. Review the pending approval steps
Open PO7624 through Recent Records or the purchase-order list. Confirm Approval Status = Pending Approval and Next Approver = Alex Morgan. Open Zone Approvals → Active Approval Logs.
Alex and Jordan each have a Pending Approval row. The order needs both obligations resolved; the two rows are not duplicate approvals by the same person.
02. Approve your assigned step and check what remains
Select Approve, refresh the same order, and return to Active Approval Logs. Alex’s row is now Approved. Jordan’s row remains Pending Approval, and Jordan is now Next Approver.
In this configured example, Alex’s ordinary Approve and Reject actions disappear after the assigned step is complete. That does not mean the whole order is approved.
03. Save the authorized employee configuration
Use global search to find Alex Morgan, open the employee, and select Edit → Approvals. In the demonstrated configuration, enable and save both Approval Manager and Super Approver Checkbox. Approval Manager provides team-approval visibility in this configuration; it is a separate setting and is not established here as a requirement for override authority.
Review existing email, sourced-approver, redirection, reset, and delegate settings without changing them. Do not add a delegate for this example.
Select Save and wait for the saved employee record. An unsaved checkbox change has not established the configured capability.
04. Return to the order and submit a reason
Return to PO7624 through Recent Records and refresh it. Jordan remains Next Approver, and Approve is now available in this configured super-approver example.
Select Approve. In Approval Reason, enter Coverage approved while assigned approver is unavailable. in Enter Reason, then select OK. This acts on the remaining step; it does not demonstrate a shortcut through an arbitrary number of approval levels.
05. Verify the order and the audit attribution
Confirm Approval Status = Approved on the same order, then open Zone Approvals → Active Approval Logs. In this replay, both rows are Approved.
On Jordan’s row, verify Approver = Jordan Reed and Overruled By = Alex Morgan. The assigned approver stays distinct from the person who acted in their place. Jordan did not personally perform this approval.
Scroll across the log if needed and verify the Approval Reason matches what you entered. Use the transaction status and individual rows together. The demonstrated Remaining Approval Logs summary still shows 1 after the override, so it is not the completion test here.
Common questions
Why is the order still pending after I approve it?
Your action may complete only your assigned step. Check the next approver and each active approval-log row to see which obligations remain pending.
Does every Administrator need Super Approver Checkbox?
Not necessarily. Default Administrator override may already be available in some ZoneApprovals configurations. Check the installed SuiteApp version, role, custom form, and your organization’s approval policy rather than assuming this checkbox is always required.
Does Approval Manager provide override authority?
In this replay, Super Approver Checkbox is associated with the demonstrated override. Approval Manager was also enabled and saved. This example does not establish that Approval Manager grants override authority or is required.
Does one override approve every remaining level?
Do not assume that it does. The demonstrated action handles Jordan Reed’s one remaining step. Review the transaction status and all remaining approval obligations after each action.
Where can I see who overrode the assigned approver?
Inspect the approval log. Approver identifies the assigned employee, Overruled By identifies the overriding actor, and Approval Reason retains the explanation. Those fields should be read together.
Is this the same as delegation or native SuiteApprovals?
No. This example uses a ZoneApprovals override. It does not configure or test delegation, or establish behavior for native SuiteApprovals routing.
Supporting references
ZoneApprovals documents the employee settings and the overrule approval process. Your installed version and role can change the labels and available actions.