Matching rules

How a matching rule works

A matching rule connects two pieces of data: one carried by the employee profile, and one carried by the opportunity (open position, training, job description, mission, etc.). When the two values match according to the criteria of the rule, the opportunity is considered accessible or relevant to the employee.

Mandatory prerequisite: for a matching rule to work, the value must exist on both sides. The employee feed must include a field carrying the value, and the same value must appear on the opportunity. Without this dual presence, the rule cannot apply.

What matching rules are used for

• Filter access to opportunities according to business criteria (population, entity, clearance, etc.).
• Refine the recommendation engine so that employees only see relevant opportunities.
• Reproduce in the platform HR or business rules already enforced in the source information system.

Use case: opportunity suggestion based on grades

Matching rules can be used to suggest opportunities through grade logic. The platform allows you to define a rule that connects an employee's grade to the grade expected on the opportunity, with configurable offsets (equality, +1, −1, range, etc.).

Concrete example

• An employee has grade 5 on their profile.
• An opportunity of type "open position" carries grade 6.
• The configured rule specifies: "the employee can see the opportunity if their grade is between opportunity_grade − 1 and opportunity_grade + 1".
• In this example, the employee (grade 5) sits within the [5; 7] range: the opportunity is suggested to them.

Several combinations are available depending on the need: strictly equal, greater than or equal, less than or equal, range. The exact configuration is set when the rule is created.

Combining rules: AND / OR

Matching rules can be combined with each other. Two distinct logics coexist and it is important to keep them apart.

Several fields used for matching = AND

When several distinct fields are used to match (for example a location field and a grade field), all rules must be satisfied at the same time. This is an AND logic: if any one rule fails, the opportunity is not suggested.

Several values inside a single field = OR

Within a single field, several values can be allowed. In that case, only one of the values needs to match for the rule to be considered satisfied. This is an OR logic.

Full example

Case 1 — Single rule, single field with several allowed values

An opportunity is open to employees based in France, Germany or the United Kingdom.

• Field used: location.
• Allowed values: France, Germany, United Kingdom.
• Behaviour: an employee based in any one of those three countries sees the opportunity. They do not need to have all three values on their profile — a single one is enough (OR logic inside the field).

Case 2 — Two rules combined on two distinct fields

An opportunity is open to employees based in France, Germany or the UK, and who are at grade 5 or 6.

• First rule — location field, values France / Germany / United Kingdom.
• Second rule — grade field, values 5 / 6.
• Behaviour: the employee must satisfy both rules at the same time (AND logic) to see the opportunity. They must therefore be based in one of the three countries AND be at grade 5 or 6. Within each rule, a single matching value is enough (OR logic).

Best practices

• Make sure the data point you intend to use is actually present in both feeds (employee and opportunity) before creating the rule.
• Use values that are normalized and consistent across both sides (e.g. ISO country codes, internal HR codes).
• Keep the number of combined AND rules on a single opportunity reasonable to avoid unintended exclusions.