CiviCRM Community Forums (archive)

I've spent a while looking around for a clear answer to this question without luck, so I apologize if it's been answered already and I just haven not hit on the right search.

Here's our situation:

We are going to have a bunch of membership types in a bunch of different organizations. We want to enable membership managers from each organization to manage memberships in their organization only, but not in other organizations. Specifically, for his/her organization:

• search members
• add, edit, delete memberships
• generate membership reports
• email members
• export membership lists
• etc.

Is this something that is possible out of the box (and if so, what's the best recipe)? If not, what custom development would need to be done to accomplish this?

Thanks.

Yes. The organizations are clubs that are sanctioned and regulated by their national sports governing body. One of the benefits of club sanctioning by the NGB is a lot of services for members of those clubs. Separate civi installs for each club would not support that objective.

We want all clubs' members in one place so we can do the NGB's service delivery. We can't do that (readily) if they're on different civi installs.

Two options that spring to mind that we have implemented for various situations where multiple layers are required.

1/ multi-org set up including both multiple drupal to single civicrm, or multiple domains on single drupal with single civicrm (using Domain Access)

2/ Organic Groups with CiviCRM, where each OG creates its own ACL group and the 'managers' of each of your orgs is made a manager of their OG and hence get access to the 'members' in civicrm

4/ Simple ACL Groups - like above but without some of the extensions that OG provides

5/ ACL Hook which provides for easy 'branch' management by limiting Person X to only see civi contacts who are marked as Branch/Org X

which we would choose will depend on a range of issues including what if any separate web 'identity' each require, what level of management the Parent Org will have versus the Children Orgs, etc.

Hope that helps open up some ideas for you.

yep sorry to have dumped that heavy explanation on you - may help if you can spell out some more scenarios - are there any other features that your separate Orgs will be getting - is it purely backend admin or are you trying to also provide some communication channels other than just a 'broadcast' of mailings out to their members?