Inbound Action - Required roles is not working as expected.DescriptionInbound Action - Required roles is not working as expected. When an inbound email action of type **Reply** is configured with entries in the **Required roles** field, the platform does not validate the sender’s roles. The action executes even if the email’s user lacks the specified role, causing unintended replies to be sent. This defect affects the Email Notifications product in the Brazil release and impacts any process that relies on role‑based filtering of inbound email actions.Steps to Reproduce 1. Create an inbound email action of type **Reply**. 2. Create a user and assign it a role that does not match any entry you will add to the action. 3. In the inbound action, add one or more roles to the **Required roles** field that the user does not have. 4. Send an email from the created user to the inbound email address.5. Observe that the inbound action executes even though the required role condition is not satisfied.Workaround1. Create a Script Include named **UserUtils** with **Accessible from** set to **All Scopes** and the following script: ```javascriptvar UserUtils = Class.create();UserUtils.prototype = {initialize: function() {},hasRole: function(userSysId, roleName) {var user = GlideUser.getUserByID(userSysId);return user ? user.hasRole(roleName) : false;},type: 'UserUtils'};```2. Open the affected inbound email action. 3. Remove all entries from the **Required roles** field. 4. In the **Condition** field, add the script: ```javascriptnew global.UserUtils().hasRole(sys_email.getValue("user_id"), "snc_external")```(Replace **snc_external** with the role you need to enforce.) 5. Save the inbound action. The action will now execute only when the sender’s user record has the specified role. *Note: This is a temporary workaround until the permanent fix is delivered in a future release as referenced in PRB1994854.*Related Problem: PRB1994854