Views:

Applies to Product- Power Automate

What’s happening?
The approval workflow fails for a user when using a custom security role that is similar to the default "Approvals User" role. The error may occur when the "Approvals User" role is not directly assigned to the user, but rather assigned via a team.


Reason:
This arises when the custom security role has been modified to include different permissions compared to the default "Approvals User" role. Specifically, if the custom role lacks necessary privileges or if the user is in a different business unit than the role being assigned, it can lead to permission errors during the approval process.


Resolution:

  1. Ensure that the "Approvals User" role is directly assigned to the user experiencing this. This can resolve the problem as the system automatically assigns this role to users who need to approve items.
  2. If using a custom role, verify that it does not modify the default "Approvals User" role. The custom role should maintain all necessary privileges required for the approval process.
  3. Check for any plugins that may be interfering with the role assignment. If there are plugins installed that affect the approval operations, consider disabling them temporarily to see if that resolves the issue.
  4. If the user is part of a different business unit, ensure that the role assignment is valid for that business unit. Users cannot be assigned roles from business units they are not part of.
  5. If the issue persists, consider creating a special role that grants the user global access to the necessary entities involved in the approval process.