BPM Prohibit User Self Approval at 'Participant' vs 'Configuration' Level

Summary:

At which level should the 'Prohibit User Self Approval' be configured and does the participant level override configuration level setting or vice versa

Content (required):

For the FINGLJournalApproval, there is the option to configure the 'Prohibit User Self-Approval' at two different levels i.e., the participant level and configuration level. Additional we found this reference (https://docs.oracle.com/en/cloud/saas/financials/23c/fafcf/prevent-assigning-approvals-to-specific-users.html#s20072141) that mentions that the participant level setting overrides the task level settings. However, during our UAT, we were not able to replicate this scenario. Could someone please provide some additional context for why the user guide mentions participant level overriding the task level settings. Essentially, we are trying to understand if we should be looking only at the task level setting or the participant level settings or both in combination for the 'Prohibit User Self-Approval' configuration