It seems like the problem is caused by the creation of the "All Roles" role that doesn't have any restrictions. When a user is a member of this role, they can see everything in the report, regardless of the RLS filters defined for other roles. To resolve this issue, you can create a separate role for those users who need to see everything, and give them access to all the data in the report without using RLS.
Alternatively, you can modify the security predicates of the existing roles to include the conditions that allow the desired users to see everything. For example, you can add an OR clause in each security predicate that checks if the current user is one of the users who need to see everything.
Here is an example of how you can modify the security predicate for the "Executive" role:
[Executive Email]= userprincipalname() OR [Email]= "<specific email of the user who needs to see everything>"
Note: Replace <specific email of the user who needs to see everything> with the actual email of the user who needs to see everything. You can do the same for other roles as well.
By modifying the security predicates in this way, you can ensure that the desired users can see everything while still using RLS to restrict access to the other users.
