When an access request is submitted, and the requester is listed as a secondary approver in the access request flow configuration, the secondary approver does not receive the task notification email.

• Okta Identity Governance Access Requests

Access Requests approver flows have built-in logic to avoid notifying a user who is already tagged in the flow. In the scenario described in the overview, the requester is already aware of the access request, and thus, notifications are not needed and are suppressed.

In most instances, this behavior is encountered during the testing of Access Request flows. In order to perform an accurate test, do not specify the requester as an approver, as the Access Requests logic is designed to suppress these notifications, and it will not lead to an accurate test of the approval notifications in a real-world scenario. Specify different accounts for primary and secondary approvers if the approval notifications are part of the test scenario.