Configuring Reminders and Escalations
Key Takeaways
Reminders notify a pending reviewer. Escalations reroute the unresolved review.
Check global settings, the request category, the requested item’s overrides and any applicable Workflow.
Use the configured time zone and Schedule Preview to verify timing before submitting a fresh test request.
Timing configuration changes apply to newly created requests. Pending requests keep their submitted configuration.
Match the control to what should happen
An approval reminder asks the current reviewer to act. An escalation routes an unresolved review to another reviewer. A timeout ends an unresolved request. Determine how long the request can reasonably remain pending, who should act at each step, and who can finish the review when the escalation chain produces no decision. Define those outcomes before adjusting time fields.
Go to Admin > Global > System Settings > Feature Settings > Approval Settings. Choose the relevant tab such as Global or Access Requests. Global timing is a starting point when no specific configuration applies. A role, access profile, or individual entitlement’s configured settings can override the global settings for that item. SailPoint specifically warns that turning off previously configured timing controls on an individual item can suppress those controls even when globally enabled. A workflow can also override global behavior. Check which approval mechanism the request actually uses and which item it submitted.
| Control | Review in the configuration | Evidence to collect |
|---|---|---|
| Reminder | Start delay, maximum count, frequency and time | Pending reviewer and reminder timestamps |
| Escalation | Initial delay, frequency, time and ordered review categories | New reviewer and escalation event |
| Fallback approver | Review category and valid resolved identity or group | Final routing when the configured chain is exhausted or a reviewer cannot be found |
| Timeout | Request expiry window, with a 90-day maximum in the documented settings | Pending state ends and follow-up reminder or escalation stops |
| Time zone | Configured zone and both schedule previews | Planned local event times and observed timestamps |
Escalation reviewers can be Manager, Identity, Governance Group, or Owners in the documented chain builder. In the documented default escalation pattern, assuming escalations are enabled and no customized settings apply, the first two escalations go to the manager of the assigned reviewer. The third goes to the fallback approver. If a reviewer cannot be found during escalation, the fallback is used. If the designated fallback has been deleted, SailPoint documents that the request remains with the last valid approver. A reviewer’s manual reassignment restarts the reminder and escalation timing, so capture it when comparing timestamps.
Work an item-specific schedule
Suppose an expense role has a stricter approval requirement than the global schedule. Configure its reminders and escalation chain under the role’s Access Requests settings. Choose the first reminder at two days, a maximum of two reminders with a daily frequency, and a first escalation at four days to a named controller. Use an independent fallback and an expiry longer than the escalation window. Treat these settings as the fictional organization’s policy. In the configured time zone, check Schedule Preview for the day and time of each planned event. Submit a new controlled request and let the reviewer remain idle. Verify both notification delivery and the actual reviewer assignment, because a reminder email and a change in assignment prove different outcomes.
Suppose an already-pending expense request used a seven-day first escalation before the edit. It still follows the previous configuration. Use the submission time and applicable settings to distinguish it from the test submitted after the change. At request expiry the reminder and escalation process stops. By default the documented inactivity timeout is 90 days. The timed expiry of an unresolved approval is distinct from an end date on an approved access assignment, which concerns removal of access.
Diagnose misrouting without conflating causes
If the anticipated reviewer never appears, start by checking whether an initial reviewer could be resolved and whether the approval is still pending. An initially missing reviewer has its own resolution sequence. For an idle, valid reviewer, inspect the escalation schedule, actual review assignment, escalation event and configured fallback. A governance group using manager-of escalation has a specific edge case. When one group member lacks a manager, their own assignment can remain while other member assignments escalate. If no members have a manager, the fallback receives the requests.
Use the access request history to find the escalated owner and resulting decision. Compare notification evidence independently if the assignment changed but the expected email did not arrive. The approval can be reassigned while an email issue still needs investigation. The provisioning activity and target then establish fulfillment after a valid decision. Separating these timestamps shows whether a defect is in routing, delivery, or the downstream write.
See SailPoint’s approval settings and escalation logic, item-level approval configuration, and request history.
At noon an administrator shortens the escalation delay for a requestable role. A request created at 9 a.m. is still pending and has not been reassigned. Which schedule applies to it?
The newly saved delay from noon
The schedule that applied when the request was submitted
The access item’s eventual end date
There is no escalation schedule because older requests are canceled on an edit
Escalations are enabled with the default routing pattern. Both manager escalation destinations and the configured fallback are valid, and nobody acts. Where does the third escalation go?
To the recipient’s selected source account
To the requester automatically
To every entitlement owner in parallel
To the configured fallback approver
Sections you finish are checked off in the contents.