Creating a new Good Guy list

You can manage your Good Guys all in the same Good Guy list.

If you use multiple compliance profiles that include different restricted party lists, then using the same Good Guy list in different compliance profiles can be problematic. This is because the Good Guy list check must be based on a unique compliance profile, which contains the same restricted party lists as the actual compliance screening. Ideally, you use a Good Guy list in exactly one profile only and also use this profile to run the Good Guy list checks.

• The Exclusive use setting prevents a Good Guy list from being used by more than one compliance profile.
  To find this setting, go to the Office − Administration − Compliance − Settings (client-specific) − open the client − Compliance screening sheet − Good Guy list settings field group.

• In the Good Guy lists overview, you will find the Used in profiles column.
  Here you can check in which compliance profiles the respective Good Guy list is used and change your settings accordingly.

Proceed as follows:

1. Select Compliance Screening – Good Guy lists.
2. Click the New button.
3. Enter a name.
4. In the Deletion settings field group, check the selected default setting, which applies only to Good Guys with condition.
   • When you work with Good Guys with condition, AEB recommends deleting them automatically to avoid unnecessary checks of Good Guys that are no longer relevant.
5. In the Check settings field group, make the necessary settings.
6. Click Save & close to save.

• For the new Good Guy list to be considered for future checks, a user with the I_COMPLIANCEADMIN role must store it in the compliance profile.

• For client settings for Good Guys with condition and Good Guy lists, go to the office − Administration − Compliance − Settings (client-specific) − open the client − Compliance screening sheet.
  For this you need either the I_COMPLIANCEADMIN or the I_ADMIN role.

How-to video

If you click the video, a request with your IP address will be transmitted to the provider. Dataprotection