Dependent custom offer fields allow organizations to control which fields (and which field options) appear during offer creation, based on values selected in other custom fields. This setup helps teams reduce clutter, avoid data entry mistakes, and guide users through only the fields relevant to the offer being built.
Create custom offer field dependency
To create a parent/child custom offer field dependency, begin by identifying the child field (the field that should appear conditionally).
Click the Configure icon on your navigation bar and select Custom Options in the left panel.
On the next page, click Offers.
Click the name of the custom offer field that should serve as the child in the dependency.
Select the Dependencies tab.
In the Define the parent field section, choose a parent field from the dropdown. The child field will appear only when a specified option is selected in this parent field.
Note:
- Only custom offer fields with the type Yes/No or Single select can be used as parent fields.
- Single select custom offer fields with more than 25 options cannot be a parent.
- For option-level filtering, the parent field type must be Single select with 25 options or fewer.
- Fields already used in a nested parent/child dependency cannot be used again as a parent.
In the Map parent options to child table, check the boxes next to each parent field option that should trigger the child field to appear.
Each selected option defaults to All options, meaning all values in the child field will be available unless you configure option-level filtering.
Click Save when finished. The parent/child dependency is now active.
When a user creates an offer, the child field will only appear if the selected parent field value matches your configuration.
Configure option-level dependencies
To limit which child field options are shown for each parent field selection:
In the Map parent options to child table, click Edit options next to a selected parent field option.
In the modal that appears, select the specific child field options that should be available when that parent value is selected.
For example, if Career Level = 3 – Senior Associate, you might include (and remove the rest):
- Annual Bonus
- Equity Grant
- Performance Bonus
Click Apply to save the configuration for that parent field option.
Repeat this process for other parent options as needed.
Click Save to finalize the full dependency setup.
Users will now see a filtered list of child field options based on the selected parent value.
Create nested parent/child dependency
Note: Greenhouse Recruiting supports a three-level nesting structure for dependent custom offer fields (i.e. grandparent/parent/child).
To create a nested dependency:
From Custom Options > Offers, click the custom offer field that serves as the parent in an existing dependency.
Open the Dependencies tab.
In the Define the parent field section, choose a new parent field. This becomes the grandparent in the hierarchy.
Note:
- Only Yes/No or Single select custom offer fields fields can be used as grandparent fields.
- Fields already in a nested structure can't be reused as grandparents.
In the Map parent options to child table, select which grandparent options should trigger the parent (and child) fields to appear.
Click Save.
Now, when users create an offer, the fields will appear only if the correct combination of grandparent and parent values is selected.
Edit or remove an existing dependency
To make changes to an existing dependency or remove it entirely, follow the same instructions above and start at the child field. Those steps are:
Go to Configure > Custom Options > Offers.
Click the name of the child custom offer field.
Open the Dependencies tab.
To edit the dependency:
Use the dropdown to change the parent field if needed.
In the Map parent options to child table, update which parent options should trigger the child field.
To change the list of visible child options for a given parent value, click Edit options and select the desired options in the modal.
Click Apply (if in the modal editing options), then Save when finished.
To remove the dependency:
In the Define the parent field section, click the X icon next to the parent field name.
In the confirmation dialog box, click Remove.
Click Save to finalize.