---
title: Applies to
slug: applies-to
docTags: 
createdAt: 2022-08-29T19:16:27.000Z
---

When you create a custom field, the first thing you'll configure is **Applies to**. This determines whether the field is attached to a person record or a job record, and that distinction shapes how data behaves across your org.

**People** — The field is tied to the individual employee. Data follows the person regardless of what role they're in. Use this for information that's fundamentally about a person, not a position.

:::BlockQuote
Examples: T-shirt size, emergency contact, preferred name, dietary restrictions, personal certifications
:::

**Jobs** — The field is tied to the position itself. If a person moves into a different role, the data stays with the job. Use this for information that describes a seat in the org, not an individual.

:::BlockQuote
Examples: Job level, cost center, headcount type, requisition ID
:::

**Not sure which to pick?** Ask yourself: would this information still apply to the person if they changed roles? If yes, it's a People field. If it describes the role or position itself, it's a Jobs field.

### Track changes over time

When **Applies to** is set to **People**, you'll see a **Track changes over time** checkbox. When enabled, every change to the field is stored with an effective date. You can view the full history of changes on a person's profile under **Personal History**.

Turn this on when you need a record of what the value was at any point in time — not just what it is today.

**Turn it on for:** Performance rating, job level, employment type, work location, visa status

**Leave it off for:** T-shirt size, dietary preference, emergency contact — data where only the current value matters

:::BlockQuote
**A note on legacy "People in jobs" fields:** If your org was set up before mid-2024, you may see fields labeled **People in jobs** in your field list. This was an older field type that is no longer available for new field creation. It has been replaced by People fields with **Track changes over time** enabled. Existing People in jobs fields continue to work, so you may see them in your custom field list, but no new fields of this type can be created.
:::