Answers.Body: <p>One comment is that it would be more common to have Contact 1 set as the Individual (current user) and Contact 2 as the Organisation.</p>
  
  <p>In terms of if an Org does not renew - if you have the Individual 'inheriting' the membership, and hence getting added to a Drupal Role via MemberSync then when the Org fails to renew then the Individual will lose any Roles other than Sync.</p>
  
  <p>An alternative would be to use Drupal Rules based on Membership Status and hence Block the user if their membership Expires but that seems unnecessary imo if you give the Authenticate role no extra permissions.</p>
  
  <p>The Individual needs to be given 'permission' over the Organisation via the Relationship, this will allow the Individual to edit some details via their CiviCRM Dashboard, though I would suggest you give them a Drupal Views block linked to a Webform and let them edit the Org details that way.</p>
  
  <p>HTH</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-26T04:51:42.857Z
Answers.Text: Thanks for your message, it has helped a lot. One key word was 'inheriting'. After some research I found the option: Relationship Type when creating a new membership type, now the individual has the same status as the org. Great! Thanks again 
Answers.UserDisplayName: samj
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-26T05:59:21.643Z
Answers.Text: Excellent - can you accept the answer - help keep SE tidy?
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-24T20:28:39.273Z
Answers.LastActivityDate: 2018-06-24T20:28:39.273Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <p>Pete's answer pretty much covers the bases - but make sure to check out the <a href="https://civicrm.org/extensions/relationship-permissions-acls" rel="nofollow noreferrer">Relationship Permissions as ACLs</a> extension, which should be a big help.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-26T04:53:15.313Z
Answers.Text: Pete's answer did cover it. I'll checkout the extension also. Thanks Jon.
Answers.UserDisplayName: samj
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-25T02:29:21.190Z
Answers.LastActivityDate: 2018-06-25T02:29:21.190Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>I am running Drupal 7 with Civi, both on the latest version. I would like a user to be able to register to become a member on behalf of an, which creates an account for a user in Drupal core, who can then edit the organisation details.</p>
  
  <p>I've setup the process so far using CiviCRM Profiles and Webforms. Here is my current setup:  </p>
  
  <ul>
  <li><p>User applies for an account using profiles and Drupal core using logintoboggan to control this part.</p></li>
  <li><p>User account is accepted, and an email is set to a webform link</p></li>
  </ul>
  
  <p>webform: Number of Contacts: 2</p>
  
  <p>1: Organisation</p>
  
  <p>2: Individual (here I have linked the Individuals Current Employer to the Organisation and added them to a group – which is used in a rule to active the user in Drupal’s core, so the user can login after completing registration)</p>
  
  <p>Users are then prompted to pay . This workflow works, mostly anyway.</p>
  
  <p>A couple of questions:</p>
  
  <p>1: Is using the method of adding the Individual to a group which activates the Drupal core user the best method? I feel that this is messy, especially when the organisations membership is due for renewal and if the organisation doesn’t renew how is the individual account deactivated? Is there a better way?</p>
  
  <p>2: How do I allow the user to edit the organisations details?</p>
  
  <p>I have many other thoughts/questions. But this enough… for now :)</p>
  
  <p>Thanks for your help!</p>
  
  <p>SJ</p>
  
Tags: <drupal><civimember>
Title: Organisation membership with Drupal user account
ThreadText: # Organisation membership with Drupal user account
  
  (Asked by: username_0 on 2018-06-24)
  
  I am running Drupal 7 with Civi, both on the latest version. I would like a user to be able to register to become a member on behalf of an, which creates an account for a user in Drupal core, who can then edit the organisation details.
  
  I've setup the process so far using CiviCRM Profiles and Webforms. Here is my current setup:
  
  * User applies for an account using profiles and Drupal core using logintoboggan to control this part.
  * User account is accepted, and an email is set to a webform link
  
  webform: Number of Contacts: 2
  
  1: Organisation
  
  2: Individual (here I have linked the Individuals Current Employer to the Organisation and added them to a group – which is used in a rule to active the user in Drupal’s core, so the user can login after completing registration)
  
  Users are then prompted to pay . This workflow works, mostly anyway.
  
  A couple of questions:
  
  1: Is using the method of adding the Individual to a group which activates the Drupal core user the best method? I feel that this is messy, especially when the organisations membership is due for renewal and if the organisation doesn’t renew how is the individual account deactivated? Is there a better way?
  
  2: How do I allow the user to edit the organisations details?
  
  I have many other thoughts/questions. But this enough… for now :)
  
  Thanks for your help!
  
  SJ
  
  **Tags:** drupal, civimember
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2018-06-24. Score: 3 | Accepted answer
  
  One comment is that it would be more common to have Contact 1 set as the Individual (current user) and Contact 2 as the Organisation.
  
  In terms of if an Org does not renew - if you have the Individual 'inheriting' the membership, and hence getting added to a Drupal Role via MemberSync then when the Org fails to renew then the Individual will lose any Roles other than Sync.
  
  An alternative would be to use Drupal Rules based on Membership Status and hence Block the user if their membership Expires but that seems unnecessary imo if you give the Authenticate role no extra permissions.
  
  The Individual needs to be given 'permission' over the Organisation via the Relationship, this will allow the Individual to edit some details via their CiviCRM Dashboard, though I would suggest you give them a Drupal Views block linked to a Webform and let them edit the Org details that way.
  
  HTH
  
  > **Comments:**
  > **username_0**: Thanks for your message, it has helped a lot. One key word was 'inheriting'. After some research I found the option: Relationship Type when creating a new membership type, now the individual has the same status as the org. Great! Thanks again   
  > **username_1**: Excellent - can you accept the answer - help keep SE tidy?  
  
  ---
  
  ### Answer by username_2 on 2018-06-25. Score: 0
  
  Pete's answer pretty much covers the bases - but make sure to check out the [Relationship Permissions as ACLs](https://civicrm.org/extensions/relationship-permissions-acls) extension, which should be a big help.
  
  > **Comments:**
  > **username_0**: Pete's answer did cover it. I'll checkout the extension also. Thanks Jon.  
  
  ---
  
  