Dependent custom offer fields allows your organization to create a nested structure of custom offer fields with defined relationships between parent and child fields. The nested structure of dependent custom offer fields creates a guided path for users when creating an offer and limits the exposure of offer fields based on the criteria you define. In this article, we will cover how to:
Note: Any custom offer field dependencies created will not be applied to existing offers. In order to apply these dependencies to an existing offer, you will need to update the existing offer.
To start, click the Configure icon 
in the upper right-hand corner and select Custom Options on the left-hand panel.
Click Offers on the subsequent page.
Create Parent/Child Dependency
When creating a parent/child dependency, you will always start at the child and define the parent from the dependency workflow. Any custom offer field type can be a child.
From the Custom Field: Offers page, click the intended child custom offer field.
Click Dependencies on the subsequent page.
Use the provided field to define the parent offer field. The child offer field will be dependent on your selected field.
Note: The following restrictions apply to parent offer fields:
- Only custom offer fields with the types Yes/No or Single select can be defined as a parent.
- Single select custom offer fields with more than 25 options will not be available to define as a parent.
- Custom offer fields that are already part of a nested parent/child dependency structure will not be available to define as a parent.
Once a parent custom offer field is selected, a subsequent section will list the options for that custom offer field. Select the custom offer field option(s) that will trigger the child custom offer field to appear.
Click Save when finished.
The parent/child custom offer field dependency is configured. This dependency will be be listed on the child custom offer field back on the Custom Fields: Offers page.
When users create an offer, the child field in the dependency you configure will only appear after the appropriate custom offer field option is selected.
Create Nested Parent/Child Dependency
Note: Greenhouse Recruiting currently supports a three-level nesting structure for dependent custom offer fields (i.e. grandparent/parent/child).
When creating a nested parent/child dependency, you will always start at a custom offer field that is a parent field in an already defined parent/child dependency.
From the Custom Field: Offers page, navigate to a custom offer field that is a parent in a parent/child dependency and click the the custom offer field name.
Click Dependencies on the subsequent page.
From the subsequent page, use the provided dropdown menu to define the parent of this offer field. In the context of the a three-tiered nesting structure, this field would be considered a grandparent custom offer field. The parent and child offer field will be dependent on the selected offer field.
Note: Only custom offer fields with the type: Yes/No or Single select can be a grandparent field. Additionally, custom offer fields that are already part of a nested parent/child dependency structure will not be available.
Once a custom offer field is selected, a subsequent section will list the options for that custom offer field. Select the custom offer field option(s) that will trigger the next subsequent generation of custom offer field to appear.
Click Save when finished.
The nested parent/child custom offer field dependency is configured. This dependency will be be listed on the child custom offer field back on the Custom Fields: Offers page.
When users create an offer, the child field in the dependency you configure will only appear after the appropriate custom offer field option is selected for the grandparent and parent fields, respectively.
