When including site users without project access in approval steps, the path can become blocked. The approvers must have project access to take action.

This occurs when picking site users during definition creation who have instance access but not access to the project where approval will run.

To avoid blocking approval paths, we should display a warning when starting a path if any approvers lack project access. For example:

"Some approvers may not have access to approve this request."