Meta Fields

This tab assigns your defined meta fields to this membership type and controls how each appears. The heading reminds you: fields that will appear on Profile and Registration forms.

👉 Before you start: The Meta Fields tab assigns fields to this membership type, but the fields themselves must be defined first under Meta Membership > Settings > Member Meta Fields. If you plan to collect custom member information, define those fields before configuring your types. See [Member Meta Fields].

Profile and Registration form lists

The tab has two independent lists, switched via the Profile | Registration toggle near the top:

• Profile — fields shown on the member’s profile/dashboard, where existing members view and edit their details
• Registration — fields shown on the sign-up form for new registrants

A field can appear on one, both, or neither. Assign fields independently to each list — you might collect a phone number at registration but expose far more detail on the profile.

👉 Member data for a field that is defined at the system level but not assigned to either a Profile or Registration form, can still be edited using from the [Edit Member Profile] admin page. In this way Meta Membership can hold member’s data that is never exposed.

Adding and ordering fields

Unused fields appear under Available fields at the bottom, each tagged with its type (text, date, phone, multi_select, and so on) and a + add button. Click + add to move a field into the active list above. Use the up/down arrows on the left of each row to set the order fields appear on the form. Click the ✕ on the right to remove a field from the list.

Per-field controls

Each assigned field has four controls:

Width — half or full. Half-width fields sit two-per-row on the form; full-width fields span the row.

Privacy — who can see this field’s value:

• all — visible to everyone
• members — visible only to logged-in members
• owner — visible only to the member it belongs to

Can edit — yes or no. Whether the member can change this field’s value themselves, or whether it’s admin-managed only.

Required — a field defined as required (tagged req) must be filled in; this is set on the field definition, not here.

Click Save Changes when done.