CiviCRM Community Forums (archive)

Hello,

I have a scenario where I need to segregate membership contacts for different chapters, so that:
- One chapter's membership director cannot see the membership info of another chapter (due to international privacy laws)
- Only the international chapter staff can see all members (as each chapter member have to agree to this data sharing policy)
- Members will have Drupal user accounts for members-only content, so we want the duplicate prevention features CiviCRM offers.

To enable this, I prefer to single, segregated database option (vs. multiple database) so we don't have to do a lot of cross DB trigger work and new db setup work as the organization doesn't have any technical staff at this time.

I wanted to run my thoughts by the people here and see if anything is missing.  My current thought is:
* Setup a single CiviCRM database and segregate it using domain IDs
* Associate the "Membership Org" in the database with the domain ID and associate power user security to this (not sure how yet, but I am hoping there is enough documentation to figure t out.  I would appreciate hints or insights however)
* Hopefully be able to associate each chapter/domain with a distinct Drupal OG for chapter members to have collaborate
* Allow any chapter's "active member" to have Member role in Drupal to access member only content
* Setup profiles for memberships to create Drupal Users (people can sign up for the site without a membership, which has much less privileges), but [and this is where I need verification/how to help] set up security so only the international staff can see Drupal Users (User to Contact executition) to detect and manage/merge multiple entries

Please let me know what you think about this and what gatcha's may be

Thanks
Sky