Custom Properties
Custom User Properties let you attach customized attributes to all People in your organization. They're one of the most powerful ways to structure your data beyond the built-in fields.
Creating Custom Properties
Navigate to People > Custom Properties and click "Add Property". Every property requires:
- 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
Field Types
Single-line Text
Short text input. Good for names, employers, IDs, or any brief free-form data.
Multiple-line Text
Longer text area. Use for notes, descriptions, or comments that may span multiple lines.
Single Checkbox
A yes/no toggle. Use for binary attributes like "Has Completed Training" or "Opted Into Newsletter".
Multiple Checkboxes
Multiple options where a person can select more than one. Good for things like "Languages Spoken" or "Skills".
Number
Numeric values only. Useful for quantities, scores, or any countable data.
Date
A date picker requiring day, month, and year. Use for "Hire Date", "Membership Anniversary", etc.
Radio Buttons
Multiple options where only one can be selected. Good for mutually exclusive categories like "Account Type: Worker / Community Supporter".
Dropdown
Same as Radio Buttons but displayed as a dropdown menu. Better for longer lists of options.
Property Settings
When creating or editing a custom property, you can configure these additional settings:
Position
Control the order properties appear in forms and on profiles. Drag and drop properties in the list to reorder them. Properties with lower positions appear first.
Requires Advanced Permission
When enabled, only Team Members with the "View Restricted Properties" permission can see this 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 in forms they're filling out on behalf of someone
Read Only
When enabled, the property value cannot be edited after it's initially set. This is useful for:
- IDs imported from external systems
- Timestamps that shouldn't change
- Data that must remain immutable for compliance
Team Members can still see read-only values, but the field will be locked for editing.
Using Custom Properties in Filters
Every custom property automatically becomes available as a filter option. Navigate to People and click "Show Filter" to see your properties listed.
| Field Type | Filter Operators |
|---|---|
| Text fields | contains, does not contain, is empty, is not empty |
| Checkbox | is checked, is not checked |
| Multiple Checkboxes | includes any, includes all, does not include |
| Radio/Dropdown | is, is not, is empty |
| Number | equals, greater than, less than, between |
| Date | is, is before, is after, is between, is empty |
Tip: Use custom properties instead of tags when you need to filter by specific values, update the data over time, or capture the information through form submissions.
Custom Properties in Forms
Custom properties can be added to any form. When someone submits a form:
- If a matching person exists, their property value is updated
- If no person exists, a new person is created with the property value
For properties with options (radio, dropdown, checkboxes), form submissions match against the option value or label. Matching is case-insensitive.
Merge Tags
Reference custom properties in emails, texts, and automations using the internal name:
{{ user.your-property-name }}
For example, a property labeled "Employer" with internal name "employer" would be:
{{ user.employer }}Updated 3 days ago
