Add custom fields to member profiles, including type, required rules, and who can see or edit each field.

Overview

Built-in profile fields are name, email, phone, and address. Custom fields cover everything else your program needs to store: an emergency contact, a membership number from a governing body, a t-shirt size, a certification date, a signed waiver, or a note only staff should see.

A custom field is part of your schema, not a free-text note. Once it exists, you can filter and export on it the same way you can on email or join date.

Define fields before you add a large number of members, especially if any of them should be required. A required field is enforced when a member is created, including on import.

Add a field

Open a member profile and use Manage in the Custom Fields section. Each field has:

Label, the name staff and members see.
Type, which controls what can be stored and how it is validated.
Help text, optional guidance shown with the field.
Required or optional. Required means a value is needed when the member is created, unless a fieldset overrides that rule.
Member visible. Whether the field appears on member-facing surfaces.
Member editable. Whether the member can set or change the value themselves.

Field visibility

Set member visible and member editable together. They control whether the member can see the field, and whether they can change it.

Member visible	Member editable	What the member can do	Example
Off	Off	Nothing. The field is staff-only.	Internal notes, vetting status
On	Off	See the value, but not change it.	Membership ID, locker number
On	On	See the value and keep it up to date in the member website and app.	T-shirt size, emergency contact

Field types

Type	Use it for
Text	A short value, such as a membership number
Text area	Longer notes
Number	A quantity or score
Checkbox	Yes or no
Date	A date without a time, such as a date of birth
Date and time	A specific moment
Select	One choice from a list
Multi-select	Several choices from a list
Email, phone, address	Extra contact details, validated as that type
Signature	A signed consent or waiver
File	An upload, such as a PDF or image

Select and multi-select need a list of allowed options. File fields can be limited to PDF, PNG, JPEG, or WebP.

Group fields into sections

A fieldset is an ordered group of fields with a name and optional description. Use fieldsets to:

Build the form staff see when creating a member, including which built-in fields are shown or required.
Attach extra questions to a product, such as a waiver that must be completed before a subscription is activated.

The member application form is made of these sections. System fields (name, email, phone, address) and custom fields can sit in the same section, in the order you want them asked.

Where the data shows up

Custom field values appear on the member profile next to the built-in fields, and on the member list so staff can see them without opening every record. They are included in search, filters, and exports.

The same definitions and values are available on the Custom Fields API and Custom Fieldsets API.

Customising Member Profile Fields