Ethical bias policies provide a way of testing your strategies for unwanted bias, as well as checking how extensive the bias is. For example, you can test whether your strategies generate biased results by sending more actions to male rather than female customers.

To edit the ethical bias policies, enable the decision/simulation/biasCheck dynamic system setting, and then grant the pzBiasPolicyConfiguration to an access group.

1. Log in to Pega Customer Decision Hub as an operator with access to Dev Studio.
2. In the navigation pane of Dev Studio, click RecordsSysAdminDynamic System Settings.
3. In the list of dynamic system settings, click the decision/simulation/biasCheck setting.
4. Set the value of the decision/simulation/biasCheck setting to true.
5. Click Save.
6. In the navigation pane of Dev Studio, click RecordsSecurityAccess Groups.
7. Edit the access group that you want to have the right to configure ethical bias policies for your organization.
   Tip: This type of access is usually granted to administrators. If required by company policies, you can create a new access group specifically for the purpose. For more information, see Creating an access group.
8. In the Available roles section, click Add role.
9. Enter a name for the new role, for example, your implementation application:MarketingBias, and then click the Open icon.
10. On the Create Access Role Name page, click Create and open.
11. Select Inherit privileges within class hierarchy, and then click Save.
12. On the Role tab, in the Access class table, click Add a row.
13. In the Add access Role Object window, in the Class field, enter @baseclass.
14. In the Access Controls section, set the value of all controls to 5.
15. In the Privileges section, click Add item, and then enter the following settings:
    1. In the Name field, enter pzBiasPolicyConfiguration.
    2. In the Level field, enter 5.
16. Click Save.
17. On the access group tab, click Save.