My question is related to how drupal users interact with their civicrm membership and contact record.
In 2013 we moved to using CiviCRM. We already had 'Group' and 'Household' membership types, so it was assumed that the Civi membership would be housed on Organisation and Household contact records, and the membership inherited by related Individual records.
However in the following years I've been wondering if we got that wrong, as there are several reasons why this doesn't work:
1) Drupal users can only be associated with an individual contact record, so they would not be able to renew a membership online if it is housed on a Household or Organisation record; they would probably end up creating a brand new membership but on their Individual record.
2) The CiviContribute pages allow for a user to join on behalf of an organisation, but when this takes place the membership is by default added to the individual's record - the relationship of 'employed by' is created by default to link to the Organisation record (which only gives inheritance to that record if the relationship for that membership is set up using that relationship.)
3) If a membership housed on an individual record is renewed online, the membership inheritance does not seem to renew the membership on the Organisation record, but at least the individual still has an active membership and therefore able to use and drupal related benefits associated with current membership.
So I am not sure how CiviCRM is actually meant to be used in this scenario - should we actually house the membership on an individual record by default and allow access via Webform to allow them to create their related Household or Organisation contact records?
Please let me know if you need any more details!