What custom fields are for
Haven stores standard information on every member record: name, email, phone, address, membership level, status, and renewal date. Custom fields cover everything else your organization tracks:- Committee or chapter assignment
- T-shirt or uniform size
- Dietary restrictions or accessibility needs
- Volunteer hours or certifications
- Emergency contact name and phone
- Professional designations or credentials
- Alumni class year or cohort
Available field types
When you create a custom field, you choose its type. The type determines how the field is displayed and what values are accepted.| Type | Best for |
|---|---|
| Text | Short answers: names, codes, single words |
| Long Text | Notes, descriptions, multi-sentence answers |
| Number | Counts, amounts, years |
| Date | Certification dates, graduation dates |
| Dropdown | Single choice from a fixed list of options |
| Multi-Select | One or more choices from a fixed list |
| Checkbox | A true/false toggle (e.g., “Newsletter opt-in”) |
| URL | Website or social profile links |
| An additional email address beyond the primary and secondary |
Creating a custom field
Enter the field name
The name is what admins and members see as the field label. Use clear, plain language: “Committee Assignment”, “T-Shirt Size”, “Graduation Year”.
Choose the field type
Select the type that matches the data you want to collect. If you choose Dropdown or Multi-Select, you will enter the available options (one per line) before saving.
Add a description (optional)
The description appears as helper text below the field. Use it to clarify what you’re asking for — for example, “Enter the committee you currently serve on, if any.”
Configure visibility and editing
Set the following options to control how the field behaves:
- Required — members cannot save their profile without filling in this field (when editable by members)
- Show in Directory — displays this field’s value on the member’s public directory entry
- Editable by Member — allows members to fill in or update this field from their portal profile
- Admin Only — hides this field from the member portal entirely; only admins can see and edit it
Filling in custom fields for members
After you create custom fields, you fill them in from each member’s profile page.Find the custom fields section
Scroll to the Custom Fields section on the profile page. All fields you have defined appear here, in the order they were created.
How custom fields appear in the member portal
When a member logs into the portal at{your-slug}.gohaven.co/portal, they see their profile page. Custom fields that have Editable by Member or Show in Directory enabled will appear in their profile.
- Fields marked Editable by Member show an edit button so members can update their own values.
- Fields marked Show in Directory appear on the member’s directory listing, visible to other logged-in members.
- Fields marked Admin Only are never shown in the portal.
Members only see and edit their own custom field values. They cannot view another member’s admin-only fields or edit anyone else’s profile.
Deleting a custom field
To remove a custom field, click the trash icon on its row in the Custom Fields table and confirm the deletion.Frequently asked questions
How many custom fields can I create?
How many custom fields can I create?
Haven does not impose a hard limit on the number of custom fields. That said, we recommend keeping the list focused — the more fields you add, the more work it is to keep them up to date. A well-chosen set of 5–10 fields serves most organizations well.
Can I reorder custom fields?
Can I reorder custom fields?
Reordering is not available in the current version. Fields appear in the order they were created. Plan your fields in the order you want them displayed before creating them.
Can I include custom fields in email merge tags?
Can I include custom fields in email merge tags?
Can I make a field required only for certain membership levels?
Can I make a field required only for certain membership levels?
Required fields apply to all members, regardless of level. If you need level-specific requirements, mark the field as not required and use admin notes or your own processes to enforce it for specific levels.