Answers.Body: <p>Reading the code, this really should be working. The webform creates the relationship via the api, which calls <a href="https://github.com/civicrm/civicrm-core/blob/4.6/CRM/Contact/BAO/Relationship.php#L53" rel="nofollow">CRM_Contact_BAO_Relationship::create</a>, which in turn calls <a href="https://github.com/civicrm/civicrm-core/blob/4.6/CRM/Contact/BAO/Relationship.php#L696" rel="nofollow">disableEnableRelationship</a> which handles related memberships. Can you check your drupal error logs for anything from the webform?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-04T14:47:21.350Z
Answers.Text: Thanks Coleman for taking the time to reply. Unfortunately nothing in the recent error logs.
Answers.UserDisplayName: Ken Truesdale
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-04T15:01:40.863Z
Answers.Text: I think I have a permissions issue.  If I add the administrator role to the user, after the membership is created, but before the webform to add a child is submitted, everything works as suspected.  Researching now on what permission is needed, but would be grateful if anybody can point me to it straight away.
Answers.UserDisplayName: Ken Truesdale
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-04T15:38:27.733Z
Answers.Text: Confirmed permission issue.  CiviMember: access CiviMember was not enabled for this role.
Answers.UserDisplayName: Ken Truesdale
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-04T02:56:37.907Z
Answers.LastActivityDate: 2015-07-04T02:56:37.907Z
Answers.UserDisplayName: Coleman
Answers.Body: <p>The CiviMember: access CiviMember permission was not enabled for the role in question.  Adding this permission solved the problem.  </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-04T16:46:13.980Z
Answers.Text: This is a good workaround but I think this is still a bug. Inherited memberships working properly should not be dependent on the permissions of whoever happens to be logged in. I'm filing an issue for this...
Answers.UserDisplayName: Coleman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-04T15:37:00.127Z
Answers.LastActivityDate: 2015-07-04T15:37:00.127Z
Answers.UserDisplayName: Ken Truesdale
Answers.Body: <p>There is a bug that requires the acting user to have "access CiviMember" permission or the inherited memberships fail to be processed. I've <a href="https://github.com/civicrm/civicrm-core/pull/6145" rel="nofollow">submitted a fix</a> for this which hopefully will be part of the next (4.6.5) release.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-07-05T21:41:06.223Z
Answers.LastActivityDate: 2015-07-05T21:41:06.223Z
Answers.UserDisplayName: Coleman
Body: <p>Civi 4.6.4 / Drupal 7.38</p>
  
  <p>Goal: Allow a constituent to add family members to their membership.</p>
  
  <p>Issue: When a constituent adds family members, via a civi web form, the relationship is created properly, however the child does not inherit the membership.  However, if as the admin, I go in and edit the relationship, make no changes, and save, the membership is now inherited properly.</p>
  
  <p>In the webform, I am adding the relationship, but not adding any membership...I'm assuming this is not necessary. The parent has an established, active membership at the time of form submission.</p>
  
  <p>Has anybody experienced this or is using another process to achieve this goal?</p>
  
  <p>Thanks,</p>
  
  <p>--Ken</p>
  
Tags: <civimember><webform-civicrm>
Title: Membership not inherited if child added via webform
ThreadText: # Membership not inherited if child added via webform
  
  (Asked by: username_0 on 2015-07-03)
  
  Civi 4.6.4 / Drupal 7.38
  
  Goal: Allow a constituent to add family members to their membership.
  
  Issue: When a constituent adds family members, via a civi web form, the relationship is created properly, however the child does not inherit the membership. However, if as the admin, I go in and edit the relationship, make no changes, and save, the membership is now inherited properly.
  
  In the webform, I am adding the relationship, but not adding any membership...I'm assuming this is not necessary. The parent has an established, active membership at the time of form submission.
  
  Has anybody experienced this or is using another process to achieve this goal?
  
  Thanks,
  
  --Ken
  
  **Tags:** civimember, webform-civicrm
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2015-07-05. Score: 4 | Accepted answer
  
  There is a bug that requires the acting user to have "access CiviMember" permission or the inherited memberships fail to be processed. I've [submitted a fix](https://github.com/civicrm/civicrm-core/pull/6145) for this which hopefully will be part of the next (4.6.5) release.
  
  
  ---
  
  ### Answer by username_1 on 2015-07-04. Score: 1
  
  Reading the code, this really should be working. The webform creates the relationship via the api, which calls [CRM\_Contact\_BAO\_Relationship::create](https://github.com/civicrm/civicrm-core/blob/4.6/CRM/Contact/BAO/Relationship.php#L53), which in turn calls [disableEnableRelationship](https://github.com/civicrm/civicrm-core/blob/4.6/CRM/Contact/BAO/Relationship.php#L696) which handles related memberships. Can you check your drupal error logs for anything from the webform?
  
  > **Comments:**
  > **username_0**: Thanks username_1 for taking the time to reply. Unfortunately nothing in the recent error logs.  
  > **username_0**: I think I have a permissions issue.  If I add the administrator role to the user, after the membership is created, but before the webform to add a child is submitted, everything works as suspected.  Researching now on what permission is needed, but would be grateful if anybody can point me to it straight away.  
  > **username_0**: Confirmed permission issue.  CiviMember: access CiviMember was not enabled for this role.  
  
  ---
  
  ### Answer by username_0 on 2015-07-04. Score: 1
  
  The CiviMember: access CiviMember permission was not enabled for the role in question. Adding this permission solved the problem.
  
  > **Comments:**
  > **username_1**: This is a good workaround but I think this is still a bug. Inherited memberships working properly should not be dependent on the permissions of whoever happens to be logged in. I'm filing an issue for this...  
  
  ---
  
  