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.

Property Groups

Once you have more than a handful of custom properties, you can organize them into groups that render as collapsible sections on every person profile. This keeps profiles tidy and lets your team focus on the properties they care about.

Creating a Group

Navigate to People > Custom Properties and click "New Group". Each group requires:

• Group Name - Displayed as the section header on profiles (e.g., "Membership Info", "Compliance")
• Group Scope - Whether the group lives at the organization level or inside a specific chapter
• Collapsed by default - When enabled, this group's section starts collapsed on member profiles. Team Members can still expand it manually.

Only Team Members at a root organization with the Add Custom Properties permission can create, rename, or delete groups.

Assigning Properties to a Group

There are two ways to put a property in a group:

1. Drag and drop. On the Custom Properties page, expand the destination group and drag a property into it.
2. Edit the property. Open the property and pick a group from the Group dropdown. Choose "Ungrouped" to remove it from any group.

A property can only be assigned to a group within its own scope. An organization-scoped group can hold any property in that organization or in its chapters. A chapter-scoped group only holds properties in that same chapter.

Profile Display

On the web dashboard, grouped properties render as a collapsible section with the group name as the header. Properties not assigned to any group appear under "Ungrouped" at the bottom. If you have no groups, profiles look exactly as they did before, no extra headers.

Deleting a Group

Deleting a group does not delete the properties inside it. They move back to "Ungrouped" and remain fully editable.

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.

💡

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 directly from the "Add New Form Field" dropdown in the form editor. Look for the Custom User Properties section of the dropdown, which lists all properties available to your organization. Select one to add it to your form.

When you add a custom property this way:

• The field's Name / ID is automatically set to the property's internal name and locked (you cannot accidentally change it)
• The field's options (for radio, dropdown, checkboxes types) are pulled from the property definition and locked
• You can still edit the label, hint, and visibility settings

When someone submits a form with a custom property field:

1. If a matching person exists, their property value is updated
2. 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.

⚠️

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:

{{ user.your-property-name }}

For example, a property labeled "Employer" with internal name "employer" would be:

{{ user.employer }}