Approval Capabilities for Users Lacking Roles in Change RequestsIssue A user without any roles can approve a Change Request if they are added to the Approvers list. ReleaseKingston Patch 3aCauseThis is standard system functionality with specific conditions.ResolutionTo test this functionality, follow these steps in a sub-production instance: Create a User with No Roles: Set up a user account without assigning any roles. Create a Change Request: Generate a test Change Request in your instance. Impersonate the No-Role User: When impersonating, the user is redirected to the Service Portal. Accessing the Change Request: The no-role user can view the Change Request and access the "Approvals" tab in the Service Portal.They cannot see or modify the list of Approvers. Admin Intervention: An admin must impersonate and add the no-role user as an approver.The approval state initially is "not yet requested." Change Approval State: The admin must change the approval state from "not yet requested" to "requested." Re-Impersonate the No-Role User: Once the state is "requested," the no-role user can see and approve the Change Request.They can only approve for themselves, not for other users. Conclusion: A user with no roles can approve a Change Request if: They are added as an approver by an admin.The approval state is changed to "requested." This behavior is consistent in an Out-of-the-Box (OOB) instance. Admin intervention is required to enable the approval process for users without roles.