Bundle member information add
When a bundle admin is adding the individual members to his/her bundle, it would be great if they only added the common fields and the membership related data is automatically copied from the admins record to the new member. This way the mandatory membership fields will only have to be filled in once and not every time a bundle member is added.
Clint Kaul commented
I'm actually in the opposite situation but I could make either solution work. We have family (parent/children) memberships. The parent has the common contact info (USmail, phone, email, ...) while the children (and parent) would have member specific details (# activities, date completed, ...).
Currently if the parent goes to add a child, they have to enter all sorts of contact info (USmail, ...) which we ignore. If they were at least pre-filled from the parent (bundle admin) that would help. I know most web browsers have auto-fill which reduces the labor.
Ideally? it would be nice to tag (in the back-end) each common field and membership field indicating whether it was shown for bundle admin, bundle member or both. Perhaps another tag (in the back-end) indicating whether a bundle member field is auto-filled from the bundle admin or not?
Nicolle Harkness commented
This would be GREAT. Currently, there is the option to limit the editing of customized membership fields to in the application, in the membership profile, or both; however, any customized membership field still shows up when a bundle administrator tries to add a member to their membership bundle! What is the point of only allowing a field to be edited in the application if it has to be re-filled in every time a member is added to a membership bundle?
This is counter-productive to trying to get members to self-service and manage their own membership bundles and if I were a bundle administrator and was being asked to fill in ALL the fields I already had to fill in on my membership application, I wouldn't bother adding new members either.
This seems like such a no-brainer and I'm shocked Wild Apricot hasn't already resolved this.