i am looking for suggestion can we limit approval escalation to 1 or at most 2 levels? It should not move further up the organization hierarchy when we set the approval reminder. Aside to workflow as solution.
Do we have any other option, we only send a reminder and skip the escalations for approval?
We had a similar requirement and implemented it using an external PowerShell script. The script tracks the escalation level and stops escalation after the configured number of levels instead of continuing up the entire management hierarchy.
Out of the box, ISC does not currently provide a native option to limit escalations to only 1 or 2 manager levels.
PUT /v2025/generic-approvals/config/ACCESS_REQUEST_APPROVAL/APPROVAL_TYPE
For reminders only, enable reminderConfig and disable escalationConfig. The request stays with the current approver and only reminders are sent.
If you want escalation but limited to 1 or 2 levels, the escalationChain in the request body controls exactly how many MANAGER_OF levels the escalation walks through. So if you put only one MANAGER_OF entry in the chain, it stops there. Once the chain is exhausted, the approval moves to the configured fallbackApprover instead of continuing further up the manager hierarchy.
Test this with a new access request, since the updated configuration does not apply to approvals already pending.
SailPoint introduced these independent reminder and escalation controls with the new approvals service in 2026.
The new reminder configuration can’t be applied retroactively to approvals that are already pending. Those approvals keep whatever reminder and escalation settings were active when they were created. SailPoint designed it this way to keep approval behavior consistent throughout a request’s lifecycle.
For existing pending requests, you can still send reminders manually from the Admin UI:
If the request has multiple approvers, open the request details and use the Assignees tab to remind the specific person. (docs reference)
Beyond that, the options are to either let the existing requests hit the timeout (default 90 days) and have requesters resubmit, or cancel and resubmit them so the new config picks up. Any newly submitted requests will automatically follow the updated reminder configuration.