Answers.Body: <p>This question gives an answer to a very similar question that you can apply to your situation: <a href="https://civicrm.stackexchange.com/questions/3590/reverse-sync-civicrm-groups-to-drupal-organic-groups">Reverse sync CiviCRM groups to Drupal organic groups</a></p>
  
  <p>However, even with a couple dozen membership types, I still think it might be better to use regular CiviMember-Role sync and use a "limit content access by role" module.  I think <a href="https://www.drupal.org/project/content_access" rel="nofollow noreferrer">Content Access</a> is the popular one.</p>
  
  <p>Try both approaches and see what works for you!</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-18T19:07:35.553Z
Answers.Text: My original approach was to use CiviMember Role Sync, which we're already using on the site and create a role for each access area, but there are potentially dozens of roles. Someone on the Drupal side suggested I try using groups. I will check out your suggestion, and I assume it will work for syncing memberships instead of CiviGroups? Thank you.
Answers.UserDisplayName: Christia
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-18T20:32:53.807Z
Answers.Text: It should!  civicrm_entity should support Memberships, so use that plus Drupal Rules module so that when a membership is created, you grant access to an Organic Group.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-18T18:13:52.917Z
Answers.LastActivityDate: 2018-01-18T18:13:52.917Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.Body: <p>Thank you for all the suggestions. I wanted to go ahead and post my solution. We ended up installing organic groups and then using the <a href="http://wiki.civicrm.org/confluence/display/CRMDOC/CiviCRM+vs.+Organic+G%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20roups" rel="nofollow noreferrer">CiviCRM OG Sync module</a> to sync the <a href="https://www.drupal.org/project/og" rel="nofollow noreferrer">Drupal organic groups</a> to CiviCRM groups. The key here is that users sign up on the Drupal end <em>first</em> and then get synced to the CiviCRM back end. </p>
  
  <p>The membership types ended up needing a lot of CMS type functionality, rather than CiviCRM membership functionality, so this worked out for us.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-02T19:32:13.270Z
Answers.Text: Good plan. FYI we have made further use of these types of features, eg synching to an OG based on Relationship, or on Event Participation in case either of those sound useful to you
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-02T17:50:51.513Z
Answers.LastActivityDate: 2018-10-02T17:50:51.513Z
Answers.UserDisplayName: Christia
Body: <p>The organization I work for wants to create a subscription that provides access to certain parts of our Drupal site using the CiviCRM membership subscription process, wherein they would subscribe to become a member of one of the memberships (there would be a couple dozen of such memberships and special access sections, one per membership type). I haven't figured out a good way to limit access to those parts of the site in Drupal and want to see if groups will do the trick. I am wondering if there is a way to sync memberships in CiviCRM with organic groups in Drupal?</p>
  
  <p>Drupal 7.56 CiviCRM 4.7.27</p>
  
Tags: <drupal><civimember><groups><roles>
Title: Way to sync CiviCRM memberships to Drupal group
ThreadText: # Way to sync CiviCRM memberships to Drupal group
  
  (Asked by: username_0 on 2018-01-18)
  
  The organization I work for wants to create a subscription that provides access to certain parts of our Drupal site using the CiviCRM membership subscription process, wherein they would subscribe to become a member of one of the memberships (there would be a couple dozen of such memberships and special access sections, one per membership type). I haven't figured out a good way to limit access to those parts of the site in Drupal and want to see if groups will do the trick. I am wondering if there is a way to sync memberships in CiviCRM with organic groups in Drupal?
  
  Drupal 7.56 CiviCRM 4.7.27
  
  **Tags:** drupal, civimember, groups, roles
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2018-01-18. Score: 1
  
  This question gives an answer to a very similar question that you can apply to your situation: [Reverse sync CiviCRM groups to Drupal organic groups](https://civicrm.stackexchange.com/questions/3590/reverse-sync-civicrm-groups-to-drupal-organic-groups)
  
  However, even with a couple dozen membership types, I still think it might be better to use regular CiviMember-Role sync and use a "limit content access by role" module. I think [Content Access](https://www.drupal.org/project/content_access) is the popular one.
  
  Try both approaches and see what works for you!
  
  > **Comments:**
  > **username_0**: My original approach was to use CiviMember Role Sync, which we're already using on the site and create a role for each access area, but there are potentially dozens of roles. Someone on the Drupal side suggested I try using groups. I will check out your suggestion, and I assume it will work for syncing memberships instead of CiviGroups? Thank you.  
  > **username_1**: It should!  civicrm_entity should support Memberships, so use that plus Drupal Rules module so that when a membership is created, you grant access to an Organic Group.  
  
  ---
  
  ### Answer by username_0 on 2018-10-02. Score: 0
  
  Thank you for all the suggestions. I wanted to go ahead and post my solution. We ended up installing organic groups and then using the [CiviCRM OG Sync module](http://wiki.civicrm.org/confluence/display/CRMDOC/CiviCRM+vs.+Organic+G%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20roups) to sync the [Drupal organic groups](https://www.drupal.org/project/og) to CiviCRM groups. The key here is that users sign up on the Drupal end *first* and then get synced to the CiviCRM back end.
  
  The membership types ended up needing a lot of CMS type functionality, rather than CiviCRM membership functionality, so this worked out for us.
  
  > **Comments:**
  > **username_2**: Good plan. FYI we have made further use of these types of features, eg synching to an OG based on Relationship, or on Event Participation in case either of those sound useful to you  
  
  ---
  
  