---
title: HRIS fields
description: Reference for which employee properties each HRIS, ATS and file source provides to Pyn, and where each one comes from in the source system.
sidebar:
  order: 3
area: integrations
feature: hris-fields
appPath: /settings/integrations/installed
lastVerified: 2026-10-22
version: "2026-10-16"
audience: admin
related:
  - integrations
  - integrations/sync-and-matching
  - directory/employees
  - directory/demographics
intercom:
  - id: "16838927"
    title: Connect to HiBob (Pyn 2)
    url: https://intercom.help/pyn/en/articles/16838927-connect-to-hibob-pyn-2
    note: draws on
  - id: "16814957"
    title: Connect to HiBob (Pyn 2)
    url: https://intercom.help/pyn/en/articles/16814957-connect-to-hibob-pyn-2
    note: draws on
  - id: "12005093"
    title: Connect to Workday (Pyn 2)
    url: https://intercom.help/pyn/en/articles/12005093-connect-to-workday-pyn-2
    note: draws on
---

Every source maps its own records onto the same set of employee properties, which is what the Directory, groups and tokens read. This table says which properties each source provides. A tick means the source maps it when the field is populated at the source; the integration's **Advanced** tab (**Fields in Report**) shows what arrived for your workspace.

## Field matrix

| Pyn property | BambooHR | HiBob | Rippling | Workday | ADP | Greenhouse | Ashby | Employee File |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Display name | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Legal name | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Preferred name | ✓ | | ✓ | ✓ | ✓ | ✓ | | ✓ |
| Work email | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Personal email | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Secondary email | | | | ✓ | | | | ✓ |
| Avatar | | | ✓ | | | | | ✓ |
| Start date | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Tenure date | | ✓ | ✓ | ✓ | ✓ | | | ✓ |
| Termination date | ✓ | ✓ | ✓ | ✓ | ✓ | | | ✓ |
| Probation end date | | ✓ | | | | | | |
| Active or inactive | ✓ | ✓ | ✓ | ✓ | ✓ | | | ✓ |
| Birthday | ✓ | ✓ | ✓ | ✓ | ✓ | | | ✓ |
| Job title | ✓ | ✓ | ✓ | ✓ | ✓ | | ✓ | ✓ |
| Department | ✓ | ✓ | ✓ | ✓ | ✓ | | ✓ | ✓ |
| Division | ✓ | | | | | | | ✓ |
| Business unit | | | | ✓ | ✓ | | | ✓ |
| Team | | | | ✓ | | | | ✓ |
| Job class | | | | | ✓ | | | |
| Location | ✓ | ✓ | ✓ | | ✓ | ✓ | ✓ | ✓ |
| Country, postal code | ✓ | ✓ | ✓ | country | ✓ | | | ✓ |
| Time zone | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Employment type | ✓ | | ✓ | | | | | |
| Employee type, worker type, time type | | | ✓ | ✓ | | | | |
| Exempt | | | ✓ | ✓ | | | | |
| Manager | ✓ | ✓ | ✓ | ✓ | ✓ | hiring manager | hiring manager | ✓ |
| HRBP | | ✓ | | | | | | ✓ |
| Buddy | | custom field | | | | | | ✓ |
| Mentor | | | | | | | | ✓ |
| Custom fields | | ✓ | | ✓ | | ✓ | ✓ | |

Custom fields are workspace extensions that Pyn support maps to a source field for you: a Bob field id, a Workday report column, a Greenhouse custom-field key or an Ashby custom field. HiBob's contract type and work office arrive this way.

## Where each source reads from

| Source | Record | Notes |
| --- | --- | --- |
| BambooHR | Employee directory or a custom report | Employment status other than Active becomes inactive; original hire date earlier than hire date marks a returning employee. |
| HiBob | People search | Start date doubles as tenure date; site is the location, falling back to address city; manager is matched by Bob id or employee id in company. |
| Rippling | Workers, with the expansions chosen on the integration | Start date doubles as tenure date; termination falls back to end date. |
| Workday | The RaaS report's columns | Column names are matched with case, spaces and underscores ignored. |
| ADP | Workers and their primary assignment | Start date is the original hire date and tenure the seniority date; workers without an email are skipped. |
| Greenhouse | Hired applications with an accepted offer | Work email is never inferred from another address type; start date is the offer's. |
| Ashby | Hired applications and their offer | Custom fields are read from the offer, then the application, then the candidate. |
| Employee File | Your spreadsheet | Column headers are the property names; `employeeId` and `primaryEmail` are required. |

## How properties are used

- Department, division, business unit, team, location, job title, employment and worker type, contract type and work office can become [demographics](https://support.pynhq.com/directory/demographics/), which create one group per value.
- Start date, termination date and the active flag set the lifecycle stage (joiner, current, on leave, terminated) that triggers and audiences use.
- Manager, HRBP, buddy and mentor are relations, available as step recipients and tokens.
- Time zone decides when a step scheduled in the recipient's time zone is delivered; see [Sync cadence and matching](https://support.pynhq.com/integrations/sync-and-matching/).

Fields from an HRIS are read-only in Pyn: a profile shows "This field cannot be modified." Change the value at the source and it updates on the next refresh. Employee File fields can be edited on the profile.

## Related

- [Integrations](https://support.pynhq.com/integrations/) for the connect guide of each source.
- [Sync cadence and matching](https://support.pynhq.com/integrations/sync-and-matching/) for schedules, matching and time zones.
- [Employees](https://support.pynhq.com/directory/employees/) for where the properties show.
- [Demographics](https://support.pynhq.com/directory/demographics/) to turn a property into groups.

## Related Intercom articles

- [Connect to HiBob (Pyn 2)](https://intercom.help/pyn/en/articles/16838927-connect-to-hibob-pyn-2) — draws on
- [Connect to HiBob (Pyn 2)](https://intercom.help/pyn/en/articles/16814957-connect-to-hibob-pyn-2) — draws on
- [Connect to Workday (Pyn 2)](https://intercom.help/pyn/en/articles/12005093-connect-to-workday-pyn-2) — draws on