Custom Properties

Custom User Properties let you attach customized attributes to People in your organization, beyond the built-in fields.


Creating Custom Properties

Navigate to People > Properties and click New property. The Properties menu item shows only for roles with the Add Custom Properties permission. Every property requires these fields, among others:

  • Label - The display name (e.g., "Account Type", "Employer")
  • Internal Name - A system identifier (auto-generated from label, used in merge tags)
  • Field Type - How the data is captured and stored

To change the order of properties in forms and on profiles, go to People > Properties at the root organization. Drag a property to a new place in the list.


Field Types

  • Single-line Text - Short free-form text, such as an employer or an ID.
  • Multiple-line Text - Longer text, such as notes or comments.
  • Single Checkbox - One yes/no checkbox, such as "Has Completed Training".
  • Multiple Checkboxes - Several options, and a person can select more than one, such as "Skills".
  • Number - Numeric values only.
  • Date - A date picker with day, month, and year.
  • Date & Time - A combined date and time picker. Automations can set it to {{now}} to stamp the current moment.
  • Radio Buttons - Several options, and only one can be selected.
  • Dropdown - Same as Radio Buttons, but displayed as a dropdown menu.
  • Object - A library of structured records that People can be linked to (see below).

Object

📘

Available on Professional plans and above.

An Object property holds a library of records, such as job titles. Each record has a Title and values for the sub-properties you define, such as a pay rate or a classification date. On a profile, team members select records from the library. Turn off Limit to One Selection to let a person hold more than one record.

On the property's settings page, click Add Record or Add Bulk Records to build the library. An archived record is hidden from future selection, and people who hold it keep their data.


Property Settings

Protected Property

When Protected Property is on, only team members whose role has the View Protected Properties permission can see and edit the property's values. Use this for sensitive data like SSN, salary information, or internal classifications that shouldn't be visible to all Team Members.

People without this permission will:

  • Not see the property on person profiles
  • Not be able to filter by this property
  • Not see the field on the dashboard Add Person form. On a page form, the field still shows.

Read-Only Property

When enabled, no one can enter or change the value by hand, not even the first value. Imports, automations, form submissions, the API, and webhooks can still write the value. Team Members can still see read-only values.


Property Groups

Groups show properties as collapsible sections on every person profile. To create a group, go to People > Properties and click New group. Only Team Members at a root organization with the Add Custom Properties permission can create, rename, or delete groups. To put a property in a group, drag it into the group on People > Properties at the root organization. You can also pick a group in the property's Group dropdown. Deleting a group does not delete the properties inside it.


Using Custom Properties in Filters and Forms

Custom properties become filter options on the People page, in the Custom Properties group of the filter field list.

To collect a property on a form, open the "Add New Form Field" dropdown in the form editor. Pick the property from the Custom User Properties section. Date & Time properties are not in the list, so a form cannot collect them.

⚠️

Common mistake: Do not use the "Custom Form Fields" section of the dropdown (text, dropdown, checkboxes, etc.) if you want data to save to a person's profile. Those generic fields store data only on the form submission, not on the person record. Always use the Custom User Properties section to create a field that writes to the person's profile.


Merge Tags

Reference custom properties in emails, texts, and automations using the internal name, with underscores changed to dashes. To get the exact tag, copy it from the Merge Tags menu in the editor:

{{ user.your-property-name }}

For Object properties, the tag outputs the title of each selected record. To output a sub-property, add it with a dot, for example {{ user.job-title.pay-amount }}.


Did this page help you?