Answers.Body: <p>Not sure yet about SE protocol but there are other options than L1 L2 etc especially if there is no requirement to have separate Drupal domains for each component. For example, we have delivered multi-level permissioned solutions using the <a href="https://civicrm.org/extensions/relationship-permissions-acls" rel="nofollow">Related Permissions</a> extension. This can go as many levels deep as required.</p>
  
  <p>For example if Org X has permissioned relationship to Org Y, which has permissioned relationship to Org Z, then any 'officer' with a permissioned relationship to an Org at any point in the hiearachy will only see the Contacts that their Org, or and sub-Orgs have permissioned relationships to.</p>
  
  <p>This is also explained <a href="https://forum.civicrm.org/index.php/topic,35633.msg151426.html#msg151426" rel="nofollow">here</a> and a blog is well overdue. Obviously if you need Drupal sites at each tier then yes the L2, L3 model is one to go for.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-20T09:50:50.753Z
Answers.Text: I can't seem to find this "Extended Permissions" extension that you mentioned. Is it the [Relationship Permissions as ACL](https://civicrm.org/extensions/relationship-permissions-acls) ?
Answers.UserDisplayName: savedario
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-20T10:20:05.130Z
Answers.Text: After reading again [this](https://forum.civicrm.org/index.php/topic,35633.msg151426.html#msg151426) I see that's the extension.
Answers.UserDisplayName: savedario
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-20T20:26:00.883Z
Answers.Text: yep sorry about misleading name - i got thrown by the phrase "Transitive permissions go only one step" and thought I was on the wrong one. Perhaps she meant 'one direction'
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-17T06:09:43.153Z
Answers.LastActivityDate: 2015-04-20T20:24:46.703Z
Answers.LastEditDate: 2015-04-20T20:24:46.703Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>I see references in the CiviCRM wiki to <a href="http://wiki.civicrm.org/confluence/display/CRMDOC/Multi-org+and+multi-site+musing" rel="nofollow">"L2" and "L3" multi-site configurations</a> - but no documentation on how to do L3 multi-site.  Can anyone explain the correct configuration for 3-level multisite?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-16T19:48:31.737Z
Comments.Text: Hi Jon - not sure yet about SE protocol but it might help to understand your needs. For example, we have delivered multi-level permissioned solutions using the Extended Permissions extension. This can go as many levels deep as required. For example if Org X has permissioned relationship to Org Y, which has permissioned relationship to Org Z, then any 'officer' with a permissioned relationship to an Org at any point in the hiearachy will only see the Contacts that their Org, or and sub-Orgs have permissioned relationships to.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-16T19:49:25.887Z
Comments.Text: May have explained it better here https://forum.civicrm.org/index.php/topic,35633.msg151426.html#msg151426 Obviously if you need Drupal sites at each tier then yes the L2, L3 model is one to go for, but can't comment on that since while we have done multiple cases for L1, L2 I don't think we have needed to provide for L3
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-16T21:20:01.450Z
Comments.Text: Pete - if you post that comment as an answer, I'll mark it as accepted!  This is very helpful, thank you.
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-17T06:11:45.267Z
Comments.Text: cool. perhaps the title should be - how to provide multi-tiered access control, since the phrase 'multi-site' does relate to L1, L2 etc
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-14T03:23:18.683Z
Comments.Text: Jon G - you were going to accept the below? and perhaps update title?
Comments.UserDisplayName: petednz - fuzion
Tags: <multisite>
Title: How to do three-tiered multi-site?
ThreadText: # How to do three-tiered multi-site?
  
  (Asked by: username_0 on 2015-04-13)
  
  I see references in the CiviCRM wiki to ["L2" and "L3" multi-site configurations](http://wiki.civicrm.org/confluence/display/CRMDOC/Multi-org+and+multi-site+musing) - but no documentation on how to do L3 multi-site. Can anyone explain the correct configuration for 3-level multisite?
  
  **Tags:** multisite
  
  > **Comments:**
  > **username_1**: Hi Jon - not sure yet about SE protocol but it might help to understand your needs. For example, we have delivered multi-level permissioned solutions using the Extended Permissions extension. This can go as many levels deep as required. For example if Org X has permissioned relationship to Org Y, which has permissioned relationship to Org Z, then any 'officer' with a permissioned relationship to an Org at any point in the hiearachy will only see the Contacts that their Org, or and sub-Orgs have permissioned relationships to.  
  > **username_1**: May have explained it better here https://forum.civicrm.org/index.php/topic,35633.msg151426.html#msg151426 Obviously if you need Drupal sites at each tier then yes the L2, L3 model is one to go for, but can't comment on that since while we have done multiple cases for L1, L2 I don't think we have needed to provide for L3  
  > **username_0**: Pete - if you post that comment as an answer, I'll mark it as accepted!  This is very helpful, thank you.  
  > **username_1**: cool. perhaps the title should be - how to provide multi-tiered access control, since the phrase 'multi-site' does relate to L1, L2 etc  
  > **username_1**: Jon G - you were going to accept the below? and perhaps update title?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-04-17. Score: 4 | Accepted answer
  
  Not sure yet about SE protocol but there are other options than L1 L2 etc especially if there is no requirement to have separate Drupal domains for each component. For example, we have delivered multi-level permissioned solutions using the [Related Permissions](https://civicrm.org/extensions/relationship-permissions-acls) extension. This can go as many levels deep as required.
  
  For example if Org X has permissioned relationship to Org Y, which has permissioned relationship to Org Z, then any 'officer' with a permissioned relationship to an Org at any point in the hiearachy will only see the Contacts that their Org, or and sub-Orgs have permissioned relationships to.
  
  This is also explained [here](https://forum.civicrm.org/index.php/topic,35633.msg151426.html#msg151426) and a blog is well overdue. Obviously if you need Drupal sites at each tier then yes the L2, L3 model is one to go for.
  
  > **Comments:**
  > **username_2**: I can't seem to find this "Extended Permissions" extension that you mentioned. Is it the [Relationship Permissions as ACL](https://civicrm.org/extensions/relationship-permissions-acls) ?  
  > **username_2**: After reading again [this](https://forum.civicrm.org/index.php/topic,35633.msg151426.html#msg151426) I see that's the extension.  
  > **username_1**: yep sorry about misleading name - i got thrown by the phrase "Transitive permissions go only one step" and thought I was on the wrong one. Perhaps she meant 'one direction'  
  
  ---
  
  