I see references in the CiviCRM wiki to "L2" and "L3" multi-site configurations - but no documentation on how to do L3 multi-site. Can anyone explain the correct configuration for 3-level multisite?
asked Apr 13, 2015 at 19:16
-
1Hi 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.– petednz - fuzion ♦Commented Apr 16, 2015 at 19:48
-
May have explained it better here forum.civicrm.org/index.php/… 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– petednz - fuzion ♦Commented Apr 16, 2015 at 19:49
-
Pete - if you post that comment as an answer, I'll mark it as accepted! This is very helpful, thank you.– Jon G - Megaphone TechCommented Apr 16, 2015 at 21:20
-
cool. perhaps the title should be - how to provide multi-tiered access control, since the phrase 'multi-site' does relate to L1, L2 etc– petednz - fuzion ♦Commented Apr 17, 2015 at 6:11
-
Jon G - you were going to accept the below? and perhaps update title?– petednz - fuzion ♦Commented May 14, 2015 at 3:23
Add a comment
|
1 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 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 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.
answered Apr 17, 2015 at 6:09
-
I can't seem to find this "Extended Permissions" extension that you mentioned. Is it the Relationship Permissions as ACL ? Commented Apr 20, 2015 at 9:50
-
-
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'– petednz - fuzion ♦Commented Apr 20, 2015 at 20:26