CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • Membership inheritance
Pages: [1]

Author Topic: Membership inheritance  (Read 1108 times)

jpb

  • I’m new here
  • *
  • Posts: 20
  • Karma: 2
    • Nightline
Membership inheritance
April 15, 2011, 03:45:49 pm
Hi

The Edit Membership Type screen allows you to cascade membership to contacts that have a relationship to a member by selecting a Relationship Type.

But what if we want those people to be members of their branch rather have a relationship with their branch?
Then we cannot have the people inherit the national membership and the access privileges that go with it - influenced by whether their branch has kept up its membership payments.

That seems logical and desirable but apparently not doable?

I don't want to use the Employer relationship because the branch is not their employer and I would quite like to record their actual employer.

James

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Membership inheritance
April 15, 2011, 06:38:43 pm
Not sure I understand your use cases completely but ... some approaches to think about:

1. If Branches are members of the National organization, then create Organization contact records for each branch, and a membership type for National membership which you use to track branch memberships.

2. Then if you have just a few branches, create a membership type for each branch where the Membership Organization is that branch. Branch members then signup for their branch's membership.

If you have more than a few branches, create one "Branch Membership" membership type and create a custom field which extends memberships of that type to store the branch organization (contact reference custom field). If you take this approach, you'll want to filter the contact reference field - which you can do via a hook). Note that there's currently a Make it Happen campaign to allow filtering within the admin UI for contact reference fields.

>> http://civicrm.org/mih#contactref
Protect your investment in CiviCRM by  becoming a Member!

jpb

  • I’m new here
  • *
  • Posts: 20
  • Karma: 2
    • Nightline
Re: Membership inheritance
April 16, 2011, 05:28:21 am
Ok thanks that pushes my thinking a bit further forward. I hadn't realised the possibility of custom data on Memberships.

Using either of the approaches you suggest how would the branch's national membership status affect the volunteer's ability to access privileged area of our Drupal site? - which should only be for volunteers at branches in good standing.

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Membership inheritance
April 16, 2011, 06:10:59 pm
I suspect you may have to extend / modify the civicrm_membership_roles module which is what folks generally use to limit content access by membership type and status. Or perhaps look at modifying the script which keeps membership statuses updated (bin/UpdateMembership.php) so that it sets a different status for branch members if their branch's national membership is not current.
Protect your investment in CiviCRM by  becoming a Member!

petednz

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4899
  • Karma: 193
    • Fuzion
  • CiviCRM version: 3.x - 4.x
  • CMS version: Drupal 6 and 7
Re: Membership inheritance
April 16, 2011, 09:32:17 pm
Dave - are you saying that you don't think Inherited Memberships work on the Memb Synch - or just highlighting the possibility that it doesnt' yet?
Sign up to StackExchange and get free expert advice: https://civicrm.org/blogs/colemanw/get-exclusive-access-free-expert-help

pete davis : www.fuzion.co.nz : connect + campaign + communicate

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Membership inheritance
April 17, 2011, 11:57:59 am
Pete - The use case above is different from inherited memberships. They're evaluating whether I'm a current member of a Branch AND whether that branch has a current National membership (as I understand what's been said). That said, I don't know if inherited memberships are currently supported by member_roles.
Protect your investment in CiviCRM by  becoming a Member!

petednz

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4899
  • Karma: 193
    • Fuzion
  • CiviCRM version: 3.x - 4.x
  • CMS version: Drupal 6 and 7
Re: Membership inheritance
April 17, 2011, 12:57:48 pm
Yeah - I guess I am at risk of making things too complicated but I was thinking along the lines that an Individual X has both a Membership to Branch Y, and gets an Inherited Membership to Org Z via a Relationship if their Membership to Branch Y is valid.

That way the standard Inherited Membership would suffice for providing denying access to specific content.

Ie if X is a direct member of Branch Y, but also has an inherited member of Org Z by dint of Branch Y being a current Member of Org Z - then you can use the Inherited Membership to run the Membership Synch from.

So if Branch Y doesn't pay up, then all Members of Branch Y lose their access.

If the above scenario is feasible, then the trick is how to ensure Individual X has the necessary relationship to Branch Y only if their direct Membership to Branch Y is valid. And I thought there may already be a hook that would do that, which might be easier than the other routes suggested.
Sign up to StackExchange and get free expert advice: https://civicrm.org/blogs/colemanw/get-exclusive-access-free-expert-help

pete davis : www.fuzion.co.nz : connect + campaign + communicate

petednz

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4899
  • Karma: 193
    • Fuzion
  • CiviCRM version: 3.x - 4.x
  • CMS version: Drupal 6 and 7
Re: Membership inheritance
June 17, 2011, 04:49:14 pm
jpb - what did you do in the end? am just looking at a scenario of Clubs being a Member of the National Association. So thinking how to make it so that Members of the Clubs are also counted as 'members' of the National Assoc.
Was thinking that if I could build a 'relationship' based on the Individuals membership of the Club - then the Inherited Membership would work if the Club is a Member of the Assoc.
Sign up to StackExchange and get free expert advice: https://civicrm.org/blogs/colemanw/get-exclusive-access-free-expert-help

pete davis : www.fuzion.co.nz : connect + campaign + communicate

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • Membership inheritance

This forum was archived on 2017-11-26.