CiviCRM Community Forums (archive)

I have configured a membership type that uses the "parent of", "step-parent of" and "foster parent of" relationships.

Then a membership is given to the individual adult.   This works as intended for the case where the only children/step children/foster children of the individual are minors residing in the household.

But, it also gives membership to grown children in the database, who should not be granted membership.

The actual membership rules for this organization is that membership should only cover children living at home with the parent.   

Some other similar membership rules:

- membership should only cover children under 20
- membership should only cover children that are full-time college students under 25 yrs. old.   

Any ideas on how to make this configurable for the person setting up their membership types?

My current work-around is to mark the "parent-child" relationship as disabled for the situation where the child should not receive -membership from the parent.   Creating additional relationship types, such as "non-dependant child" would be a decent work-around too.

What I am trying to plan is a better, longer term solution that does not cause any client-training issues or extra work.  For example, the relationships are originally set up by the staff when the children are young and should be covered by the parent's membership.   I just don't think anyone will remember to ( or have the time to) go back and change the relationship type when the kid grows up and moves out or ages out.

One idea I had was to have additional configuration choices in the admin area for membership types.