Granular Delegation Not Applying to Existing Approvals<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Overview This article explains why Granular Delegation in ServiceNow does not apply to existing approvals, and what options are available to address this. Why It Happens When a delegation rule is created, the system applies it to new approval records generated after the rule takes effect.Approval records that already exist at the time of rule creation do not update automatically.This is by design, as delegation is enforced during approval record creation, not retroactively. Example Scenario User A has several pending approvals created yesterday.Today, an administrator sets up a granular delegation so User B can act on User A’s approvals.Result: Any new approvals created for User A after the rule was enabled can be delegated to User B.Any existing approvals remain visible only to User A unless reassigned. Resolution / Workarounds If granular delegation needs to apply to existing approvals: Reassign the approval manually Navigate to the approval record (sysapproval_approver table).Update the Approver field to the delegated user. Regenerate the approval Cancel the existing approval and trigger the workflow/flow again so that a new approval is created under the active delegation rules.