Default Field Paths

Each field has a path (what you reference) and a label (what the picker shows). Paths are grouped by the object they belong to: the employee, employer, client, or job connected to the placement.

Employee

Path	Label
employee.first_name	First Name
employee.middle_name	Middle Name
employee.has_middle_name	Has Middle Name
employee.last_name	Last Name
employee.email	Email
employee.phone	Phone
employee.date_of_birth	Date of Birth
employee.social_security_number	Social Security Number
employee.address	Employee Address

Employer

Path	Label
employer.name	Employer Name
employer.ein	Employer EIN
employer.address	Employer Address
employer.id	Employer ID

Client

Path	Label
client.name	Client Name
client.id	Client ID

Job

Path	Label
job.name	Job Name
job.address	Job Address
job.id	Job ID

Address Components

An address fact ("employee.address", "employer.address", "job.address") expands into components you can reference individually:

.street
.secondary
.city
.state
.zip
.country

For example, "employee.address.state" references just the employee's state, and "job.address.state" references the state of the job.

Custom Attributes

Anything beyond the above default list is a custom attribute you can define on your account. Once created, a custom attribute is referenceable just like a built-in fact, under its entity's "custom_attributes" namespace:

employee.custom_attributes.{name}
employer.custom_attributes.{name}
client.custom_attributes.{name}
job.custom_attributes.{name}

Custom attributes appear in the picker alongside the default facts on your account's own forms. They are not available on global forms, which can only reference the default facts above.

*Note* Placement custom attributes (placement.custom_attributes.*) are not referenceable on form fields or in content variables. They live in the policy and rules layer, where they decide which forms get assigned.

For more information, please see the article titled Onboarding - Policy Rule Operators.

Onboarding - Default Field Paths