Hi Team, through testing, we've confirmed:
- Delegation only works if the delegate is already listed as an authorized approver (in the Approval Map or Workgroup) for that step. Delegating to someone outside the map/workgroup has no effect - they can't see or act on the item, even though the delegation is saved.
- If a person is already a listed approver/workgroup member, they can approve on a colleague's behalf regardless of whether delegation was set up at all - simply because they're already authorized.
- This raises the question: what scenario is Delegation actually solving, if a Workgroup member doesn't need to be delegated to act, and a non-Workgroup member can't act even if delegated?
Is Delegation intended for a narrower use case - for example, routing to a specific single person outside the group (rather than "any workgroup member"), or perhaps intended for approval maps that use a single named Employee approver (not Workgroup-based) so there's normally no built-in backup? Any clarification on the intended design/use case would help us decide whether to build our processes around Delegation or purely around Workgroups.
FYI - we are currently on 2025 R1 and will be upgrading to 2026 R1 this October. Does 2026 R1 include any fix, enhancement, or solution addressing this
