How to access
Settings → Users & Profiles → Profile FieldsAvailable Fields
The same fields available for registration can be enabled for profiles:Personal Information
- First Name, Last Name
- Birthday, Gender
- Phone Number
- Address, Postal Code
- Town (birth and current)
- Location on members map
Professional Information
- Profession headline
- Industry/sector
- Company details
- Current organization and role
Social Profiles
- Website, Facebook, Twitter/X, LinkedIn
- Instagram, Telegram, TikTok
- Signal, Bluesky
Field Configuration Options
For each field, you can configure:Enable/Disable
Toggle whether the field appears on user profiles.Required
Mark fields as mandatory. When a field is required: This is useful for collecting information that wasn’t required at registration but is needed later.Immutable (Custom Fields Only)
For custom fields, you can mark them as immutable. Once a user sets an immutable field value, they cannot change it themselves - only administrators can modify it. Use cases for immutable fields:- Membership number (assigned once)
- Original join date
- Verified credentials
Custom Fields on Profiles
Custom fields created for your organization can also be added to user profiles.| Option | Description |
|---|---|
| Enabled | Field appears on the profile edit form |
| Required | User must fill this field |
| Immutable | User cannot change after initial entry |
| Admin Only | Only visible to administrators (marked with green “admin” tag) |
Required Fields Workflow
When you mark a field as required:Profile vs Registration Fields
| Aspect | Registration Form | Profile Fields |
|---|---|---|
| When shown | During sign-up | After login, on profile page |
| Purpose | Initial data collection | Ongoing profile management |
| Required fields | Block registration | Trigger splash screen on login |
| Immutable option | Not available | Available for custom fields |
A field can be on both forms with different settings. For example, phone might be optional at registration but required on profiles.
Best Practices
Don't require too many fields
Don't require too many fields
Every required field adds friction. Only require fields that are truly essential for your organization’s operations.
Use required fields for compliance
Use required fields for compliance
If you need certain data for legal or organizational compliance, make those fields required on profiles to ensure collection.
Consider progressive profiling
Consider progressive profiling
Start with minimal required fields at registration, then use profile requirements to collect additional data over time.
Use immutable fields carefully
Use immutable fields carefully
Only make fields immutable when there’s a clear reason (e.g., membership ID, verified data).
Related Settings
- Registration Form - Fields shown during sign-up
- Custom Fields - Create organization-specific fields
- Privacy Settings - Control who can see profile data