Understand how dependent fields in Bob behave when values are auto-populated from Greenhouse.
When you map fields from Greenhouse to Bob and use them in a new hire flow, any field dependencies you’ve configured in Bob (like site → company ID or cost centre → department) are still enforced—even when the data is auto-populated.
Here’s what to expect:
When Greenhouse sends candidate data, mapped fields are prefilled in the new hire flow.
Bob applies dependency validation during the flow itself (not at the moment of data import).
This means the relationship between primary and dependent fields is checked just like it would be for manual entry.
So in your examples:
If site is filled, Bob will validate that the selected company ID matches the dependency setup.
If cost centre is filled, Bob will validate the corresponding department.
If something doesn’t match your dependency rules:
The flow will flag a validation error.
The profile can’t be completed until the mismatch is corrected.
A few things to double-check to make this work smoothly:
Values sent from Greenhouse must exactly match the values configured in Bob (including spelling and formatting).
Both the primary and dependent fields need to be included in the new hire flow.
Your field mappings in the integration should cover both sides of the dependency.
If Greenhouse sends a value that doesn’t align with your dependency setup, Bob won’t silently accept it - the validation will catch it during the flow.