What occurs if a request submitted has SOD violations and the approver is the requestor?

When a request is submitted and it contains Segregation of Duties (SOD) violations with the requestor also acting as the approver, the system is designed to enhance security and compliance. SOD violations indicate that a user is trying to perform actions that could lead to conflicts of interest or fraudulent activities—essentially allowing them to control multiple aspects of a transaction or process which could lead to abuse.

In such scenarios, the correct course of action is typically to deny the request. This built-in governance ensures that no individual can approve actions that may compromise the integrity of the system or expose it to risks. The function of denying the request in this case is a safeguard against potential internal fraud or errors that could arise when a requestor also has the power to approve their own requests. This policy serves as a foundational principle in identity governance to maintain appropriate checks and balances within the organization.