Role-Based Permissions Supports Excluding Access by Person
Description
As a Role-Based Permissions administrator, when you create or edit a role assignment, you can choose to exclude the granted users from accessing their own data in the Define a Target Population step. Previously, you could only exclude a user from accessing his or her own data by employment. Now, you can exclude a person from accessing his or her own data by person, which means the person can't access data of all his or her employments.See More
Detailed Description
As a Role-Based Permissions administrator, when you create or edit a role assignment, you can choose to exclude the granted users from accessing their own data in the Define a Target Population step. Now, you can exclude a person from accessing his or her own data by person, which means the person can't access data of all his or her employments. If Exclude by User is selected, a user in the access population can't access his or her own data of the selected employment.
Impact Assessment
This feature has limited impact but should be reviewed to confirm alignment with business processes in Identity and Access Management implementations. As a Role-Based Permissions administrator, when you create or edit a role assignment, you can choose to exclude the granted users from accessing their own data in the Define a Target Population step. Now, you can exclude a person from accessing his or her own data by person, which means the person can't access data of all his or her employments. Implementation teams should verify that existing configurations remain valid and test core business scenarios after the upgrade to confirm correct behavior.