Author Topic: Committee Roles Revisited (Read 478 times)

NASACT · October 04, 2012, 09:46:48 am

So I was looking through an old post http://forum.civicrm.org/index.php/topic,8292.msg35856.html#msg35856 and it seems as though this matches what I am trying to do. Since the post is rather old I wanted to revisit this and see if anyone has any updates to these ideas. Plus it's always good to review my understanding of the best approach.

Goal: To create a group to be used for a Committee in which individuals can be attached to, role assignments and access control.

Is the best way to create an organization that is the committee and attach people to it and create new household relationships such as "Chair" and assign those to each individual then add the organization to a static group of the same committee name and use Role Sync to accomplish access control on the CMS(my case is drupal) side of things?

As always, thank you to whomever responds.

adixon · October 04, 2012, 12:31:46 pm

For longer term scalability, i'd recommend you don't use Drupal roles to distinguish your board members, but instead use organic groups and the og <-> civicrm group synchronization.

That synchronization works in both directions - so you can manage membership from either Drupal (whether or not they are in the corresponding organic group) or CiviCRM (include or not in the civicrm group).

NASACT · October 04, 2012, 01:52:52 pm

So could you describe this setup that you are proposing with OG's, how does it handle positions within the groups?

Thanks!

adixon · October 04, 2012, 02:23:42 pm

Well, I can't really give you a one-size fits all solution ... it really depends on what sort of privileges you want to associate with different roles in your committees.

If it's just a question of different people within the committee having different access based on subcommittee membership, then that's pretty straightforward using different OG groups for each subcommittee.

I guess the short version is that the OG solution is really geared toward differential read access, not so much to other kinds of site privilege.

If you have a few 'super' board members with special civicrm access for example, then roles makes sense as a tool for giving different access.

CiviCRM Community Forums (archive)

News:

Author Topic: Committee Roles Revisited (Read 478 times)

NASACT

Committee Roles Revisited

adixon

Re: Committee Roles Revisited

NASACT

Re: Committee Roles Revisited

adixon

Re: Committee Roles Revisited