Custom fields

Custom fields let you collect data on member profiles that GreekManage doesn't include by default — pledge class, big-little assignment, T-shirt size, emergency contact, etc.

Who can use this

Available to: Org / National Admins.

Open custom fields

Org → Settings → Custom fields.

You'll see all fields configured for your org, with type, visibility, and required status.

The custom fields list.

Create a custom field

1. Click New field.
2. Set:
   • Label (what members see — e.g., "Emergency contact")
   • Field key (machine-readable; auto-generated from label, used in CSV import)
   • Type:
     • Text (short or long)
     • Number
     • Date
     • Single-select dropdown
     • Multi-select
     • Checkbox
     • URL
   • Required? — must be filled before profile is "complete"
   • Visibility:
     • Member sees and edits (default)
     • Member sees, officer edits
     • Officer sees and edits (member doesn't see at all)
     • Org admin only
   • Help text (shown under the field on the profile editor)
3. For dropdown/multi-select, list the options.
4. Click Save.

The field appears immediately on every member profile.

Edit or remove a field

1. Open the field from the list.
2. Click Edit to change label, options, visibility.
3. Click Delete to remove the field.

Deleting fields is destructive

Deleting a field also deletes all the values members have stored in it. Export to CSV first if you want to preserve the data.

Reordering

Drag fields by their handle in the list to reorder them on the profile editor. Field order matters for first-time setup flows.

Required fields and the completeness score

If you mark a field required, it counts toward the profile completeness score:

• Members with all required fields filled: 100%
• Each missing required field deducts proportionally.

Configure how scoring weights work in Org → Settings → Profile completeness.

Use cases

Field	Type	Visibility
Pledge class	Text	Member sees, officer edits
Big	Member picker	Member sees, officer edits
Emergency contact name	Text	Officer + admin only
Emergency contact phone	Text	Officer + admin only
T-shirt size	Single-select (S, M, L, XL, XXL)	Member sees and edits
Dietary restrictions	Multi-select	Member sees and edits
Notes (private)	Long text	Org admin only
LinkedIn URL	URL	Member sees and edits

Custom fields in CSV import

Each custom field gets a column in the import template, named custom_<field_key>. Values must match the type:

• Single-select: exact match to one of the options
• Multi-select: pipe-separated (option1|option2)
• Checkbox: true / false
• Date: YYYY-MM-DD

→ Member CSV import

Custom fields in exports

When you export the member directory or run a report, custom fields are included as columns.

Tips

• Start with the minimum. Add fields as you find you need them, not preemptively.
• Use field keys carefully. Once set, changing the key breaks CSV imports and integrations.
• Mark sensitive fields admin-only. Emergency contacts, medical info, financial info shouldn't be visible to peers.

Related

• Member CSV import
• Branding & profile completeness