- Environment:
- EU
- UAE
- US
Refer to the following list of properties for individuals and matching rules when creating branch elements.
- Environment:
- EU
- UAE
- US
This is the role an associate holds in a company.
In Maxsight, you can see the Associate role field by going to an individual's assessment. It's displayed in the Overall status section.

If the Associate role field is not present, the individual is not an associate and they are classified as None for the purposes of the matching rule.
Note
The API 4.0 field for Associate role is linked_to.roles
. The API 3.5 field is applications.associated_role
.
Matching rule | Behavior | Example |
---|---|---|
Associate role is one of:
Note that you can select multiple associate roles. | If the individual holds any of the specified associate roles, the assessment takes the Yes branch. | Associate role is one of Authorized person, Director:
|
Associate role is not one of:
Note that you can select multiple associate roles. | If the individual does not hold any of the specified associate roles, the assessment takes the Yes branch. | Associate role is not one of Authorized person, Director:
|
- Environment:
- EU
- UAE
- US
The risk level of the assessment.
In Maxsight, you can see the risk level by going to an individual's Assessment risk scores.
The API field for the risk level is applications.risk.overall.level
. To get a notification when a risk level changes, use the risk level changed webhook.
Matching rule | Behavior | Example |
---|---|---|
Risk level is one of:
Note that you can select multiple risk levels. | If the assessment has any of the specified risk levels, the assessment takes the Yes branch. | Risk level is one of High, Medium:
|
Risk level is not one of:
Note that you can select multiple risk levels. | If the assessment does not have any of the specified risk levels, the assessment takes the Yes branch. | Risk level is not one of High, Medium:
|
- Environment:
- EU
- UAE
- US
The risk score of the assessment.
In Maxsight, you can see the risk score by going to an individual's Assessment risk scores.
The API field for the risk score is applications.risk.overall.score
.
Matching rule | Behavior | Example |
---|---|---|
Risk score is less than: A number | If the assessment's risk score is less than the specified number, the assessment takes the Yes branch. | Risk score is less than 100:
|
Risk score is less than or equal to: A number | If the assessment's risk score is less than or equal to the specified number, the assessment takes the Yes branch. | Risk score is less than or equal to 100:
|
Risk score is greater than: A number | If the assessment's risk score is greater than the specified number, the assessment takes the Yes branch. | Risk score is greater than 0
|
Risk score is greater than or equal to: A number | If the assessment's risk score is greater than or equal to the specified number, the assessment takes the Yes branch. | Risk score is greater than or equal to 0:
|
Risk score is in the range: A number ≤ value ≤ A number | If the assessment's risk score is within the specified range, including the start number and end number, the assessment takes the Yes branch. | Risk score is in the range 0 ≤ value ≤ 100:
|
Risk score is in the range: A number < value < A number | If the assessment's risk score is within the specified range, excluding the start number and end number, the assessment takes the Yes branch. | Risk score is in the range 0 < value < 100:
|
Risk score is in the range: A number ≤ value < A number | If the assessment's risk score is within the specified range, including the start number and excluding the end number, the assessment takes the Yes branch. | Risk score is in the range 0 ≤ value < 100:
|
Risk score is in the range: A number < value ≤ A number | If the assessment's risk score is within the specified range, excluding the start number and including the end number, the assessment takes the Yes branch. | Risk score is in the range 0 < value ≤ 100:
|
- Environment:
- EU
- UAE
- US
The age of the individual.
The age is determined by taking the individual's Date of birth field and calculating the number of years between that date and today.
The individual's Date of birth is stored in their Entity data. The API field for Date of birth is collected_data.personal_details.dob
.
Matching rule | Behavior | Example |
---|---|---|
Age is less than:
| If the individual's age is less than the specified number, the assessment takes the Yes branch. | Age is less than 25:
|
Age is less than or equal to:
| If the individual's age is less than or equal to the specified number, the assessment takes the Yes branch. | Age is less than or equal to 25:
|
Age is greater than:
| If the individual's age is greater than the specified number, the assessment takes the Yes branch. | Age is greater than 18:
|
Age is greater than or equal to:
| If the individual's age is greater than or equal to the specified number, the assessment takes the Yes branch. | Age is greater than or equal to 18:
|
Age is in the range:
≤ value ≤
| If the individual's age is within the specified range, including the start number and end number, the assessment takes the Yes branch. | Age is in the range 18 ≤ value ≤ 25:
|
Age is in the range:
< value <
| If the individual's age is within the specified range, excluding the start number and end number, the assessment takes the Yes branch. | Age is in the range 18 < value < 25:
|
Age is in the range:
≤ value <
| If the individual's age is within the specified range, including the start number and excluding the end number, the assessment takes the Yes branch. | Age is in the range 18 ≤ value < 25:
|
Age is in the range:
< value ≤
| If the individual's age is within the specified range, excluding the start number and including the end number, the assessment takes the Yes branch. | Age is in the range 18 < value ≤ 25:
|
- Environment:
- EU
- UAE
- US
The email address of the individual.
The individual's Email address is stored in their Entity data.
The API field for Email address is collected_data.contact_details.email
.
Matching rule | Behavior | Examples |
---|---|---|
Email starts with:
(case insensitive) | If the individual's email address starts with the specified letters/numbers/symbols, the assessment takes the Yes branch. Letter case does not need to match. | Email starts with alex (case insensitive): The assessment follows the Yes branch if, for example, the individual has any of these email addresses: alex@forexo.com, alexa@aerialtraders.com, or ALEX@FOREXO.COM. It follows the No branch if, for example, the individual has darcy.alex@forexo.com. |
Email starts with:
(case sensitive) | If the individual's email address starts with the specified letters/numbers/symbols, the assessment takes the Yes branch. Letter case must match exactly. | Email starts with alex (case sensitive):
|
Email ends with:
(case insensitive) | If the individual's email address ends with the specified letters/numbers/symbols, the assessment takes the Yes branch. Letter case does not need to match. | Email ends with @forexo.com (case insensitive):
|
Email ends with:
(case sensitive) | If the individual's email address ends with the specified letters/numbers/symbols, the assessment takes the Yes branch. Letter case must match exactly. | Ends with @forexo.com (case sensitive):
|
Email contains:
(case insensitive) | If the individual's email address contains the specified letters/numbers/symbols, the assessment takes the Yes branch. Letter case does not need to match. | Email contains .com (case insensitive):
|
Email contains:
(case sensitive) | If the individual's email address contains the specified letters/numbers/symbols, the assessment takes the Yes branch. Letter case must match exactly. | Email contains .com (case sensitive):
|
Email is equal to:
(case insensitive) | If the individual's email address matches the specified letters/numbers/symbols exactly, the assessment takes the Yes branch. Letter case does not need to match. | Email is equal to alex@forexo.com (case insensitive):
|
Email is equal to:
(case sensitive) | If the individual's email address matches the specified letters/numbers/symbols exactly, the takes the Yes branch. Letter case must match exactly. | Email is equal to alex@forexo.com (case sensitive):
|
Is one of:
Note that each email address should be on a new line. | If the individual's email address matches any of the email addresses exactly, the assessment takes the Yes branch. Letter case must match exactly. | Email is one of alex@forexo.com:
|
Is not one of:
Note that each email address should be on a new line. | If the individual's email address does not match any of the email addresses exactly, the assessment takes the Yes branch. Letter case must match exactly. | Email is not one of alex@forexo.co.uk, ALEX@FOREXO.CO.UK:
|
- Environment:
- EU
- UAE
- US
The nationality of the individual.
The individual's Nationality is stored in their Entity data.
The API field for Nationality is collected_data.personal_details.nationality
.
Matching rule | Behavior | Example |
---|---|---|
Nationality is one of:
Note that you can select multiple countries. | If the individual's country of nationality matches one of the specified countries, the assessment takes the Yes branch. | Nationality is one of Canada, United States:
|
Nationality is not one of:
Note that you can select multiple countries. | If the individual's country of nationality does not match one of the specified countries, the assessment takes the Yes branch. | Nationality is not one of No state:
|
- Environment:
- EU
- UAE
- US
Any PEPs, sanctions, watchlist, internal watchlist, or adverse media matches the individual has.
The individual's risk screening matches are stored on their Assess PEPs, sanctions, and adverse media task.
The API object for risk screening matches is events
.
Matching rule | Behavior | Example |
---|---|---|
One or more confirmed matches are:
Note that you can select multiple match types. | If the individual has any confirmed matches with the specified types, the assessment takes the Yes branch. | One or more confirmed matches are PEP, Sanction:
Note that the assessment will only follow a branch path when there are no potential matches left. |
One or more potential matches are:
Note that you can select multiple match types. | If the individual has any potential matches with the specified types, the assessment takes the Yes branch. | One or more potential matches are PEP, Sanction:
|
Potential, confirmed, or ignored matches are:
Note that you can select multiple match types. | If the individual has any risk screening matches, ignored, potential, or confirmed, with the specified types, the assessment takes the Yes branch. | Ignored matches, and potential or confirmed matches are PEP, sanction, watchlist, or internal watchlist:
|
If any additional screening matches are returned during ongoing monitoring, the assessment returns to this branch point and is re-evaluated using the new matches.
- Environment:
- EU
- UAE
- US
The country present in the individual's current address.
The individual's Address is stored in their Entity data.
The API field for Address is collected_data.address_history
.
Matching rule | Behavior | Example |
---|---|---|
Is one of:
Note that you can select multiple countries. | If the individual's current address has a country that matches one of the specified countries, the assessment takes the Yes branch. | Is one of Canada, United States:
|
Is not one of:
Note that you can select multiple countries. | If the individual's current address has a country that does not match one of the specified countries, the assessment takes the Yes branch. | Is not one of No state:
|
- Environment:
- EU
- UAE
- US
You can add branch elements for any of your custom fields.
The matching rules you can use depend on the custom field's content type.
- Environment:
- EU
- UAE
- US