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) »
  • Inherited Membership - Relationship - On Behalf Off - Clarification
Pages: [1]

Author Topic: Inherited Membership - Relationship - On Behalf Off - Clarification  (Read 1254 times)

Traveler777

  • I post occasionally
  • **
  • Posts: 43
  • Karma: 0
  • CiviCRM version: 3.3.2
  • CMS version: Drupal 6.2
Inherited Membership - Relationship - On Behalf Off - Clarification
December 12, 2010, 05:28:37 pm
Hi All,

I am new to CiviCRM and Drupal. Coming from Blackbaud and their (Kintera) Sphere CMS/CRM.

Good to be here and now my question:

I was reading up on the inheriting membership options and was wondering, if you offer x amount of individual memberships with an organizational membership, what are the best practices to apply the relationship to those, besides the individual main contact that signs up "On Behalf Off"? Do we need to apply the relationships by hand to inherit the memberships? If this is the case, how do they sign up, if the contribution page requires payment?

Sorry, I am lost here and couldn't figure this out while reading through other posts on this topic. Also can anyone recommend some best practice examples for member sign up structure (individual - organization)?

Thank you and happy to be here :)

Traveler777

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: Inherited Membership - Relationship - On Behalf Off - Clarification
December 12, 2010, 07:41:36 pm
Welcome

Are you saying you only want to give a certain number of inherited memberships per organisation - not doable out of the box.

You could have them sign up, using Current Employer field - and then manually allocate the correct number of inheritied memberships based on a different Relationship.

Or see if someone comes along who has already done the 'set a cap' approach to an inherited membership - can't recall seeing one though.
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

Traveler777

  • I post occasionally
  • **
  • Posts: 43
  • Karma: 0
  • CiviCRM version: 3.3.2
  • CMS version: Drupal 6.2
Re: Inherited Membership - Relationship - On Behalf Off - Clarification
December 13, 2010, 10:40:27 am
Thanks Peter. Let's say for the ease of it, all employees of company x can become a member when their organization joins. Does the relationship to inherit membership need to be applied manually to every employee?

Some thoughts: (background: we have one individual and one organizational membership level)

1) Main contact signs up organization x for membership (on behalf off function)
>> Organization becomes organizational member - main contact inherits organizational membership through relationship

So far so good. One questions that comes to mind, is there a way to apply an individual membership to the person who signed up the organization, since he represents an individual?

2) X number of employees receive the privilege to become a member of the organization. How do they sign up to become a member, if the contribution page requires payment? I can see two options. (1) include custom fields in organization sign up form to collect name and email and have admin register by hand and apply relationship (2) have a separate, hidden application form, which does not include payment, and allows employees to sign up and apply relationship by hand.

>> Both options are not ideal, so I was wondering how other member organizations out there have set up their registration process?

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: Inherited Membership - Relationship - On Behalf Off - Clarification
December 13, 2010, 10:45:34 am
Hi T.

So Person A signs up for Org A.

If the Membership is based on the 'employer of' relationship then anyone who comes along and signs up on a non-membership profile and puts Org A as their 'current employer' will inherit the Membership.

ie for the Individuals they don't need to be signing up for a Membership, they just need to get in to your DB with ORG A as their employer and the inherited membership does the rest.

Hope that helps.
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

Traveler777

  • I post occasionally
  • **
  • Posts: 43
  • Karma: 0
  • CiviCRM version: 3.3.2
  • CMS version: Drupal 6.2
Re: Inherited Membership - Relationship - On Behalf Off - Clarification
December 13, 2010, 11:20:17 am
I am getting there. Thanks again.

"...anyone who comes along and signs up on a non-membership profile and puts Org A as their 'current employer' will inherit the Membership."

Does the field "current employer" automatically check for org records? How does Person A inherit the Org A membership automatically?

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: Inherited Membership - Relationship - On Behalf Off - Clarification
December 13, 2010, 11:28:20 am
Hi Tim

Recommend you read the chapter in the book - http://en.flossmanuals.net/CiviCRM/MembershipSignup

Have you tried setting up inherited membership on the demo? And a Profile with a Current Employer field in it?

Current Employer is not a Auto Reference field no. So people need to enter the correct name. I suspect this can be worked around provided the Orgs in the db are not concerned about being identified through that mechanism.
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

Traveler777

  • I post occasionally
  • **
  • Posts: 43
  • Karma: 0
  • CiviCRM version: 3.3.2
  • CMS version: Drupal 6.2
Re: Inherited Membership - Relationship - On Behalf Off - Clarification
December 13, 2010, 11:43:28 am
Yes, I did read the book. Great work. Love it. PS - I think there is some content missing here: http://en.flossmanuals.net/CiviCRM/MembershipPlanning on the ASPTA example.

Yes, we did some test Profiles in regards to inheriting memberships, but will give it another shot.


Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • Inherited Membership - Relationship - On Behalf Off - Clarification

This forum was archived on 2017-11-26.