Author Topic: Oh behalf of, inherited memberships, and permissions relationships (Read 1161 times)

petednz · September 05, 2011, 01:37:22 pm

HI - was running in to some problems that the 'on behalf of' org wasn't prefilling when I created the original Org membership at backend - via import.

I thought it was to do with Permissioned Relationship - but realised that this is not the Relationship that we are using for the inherited membership - but the 'employer of' relationship that needs to be created and permissioned if we want IndivA to have OrgA prefilled when they go to Renew.

So maybe I should check Wiki and confirm the documentation, though I would suggest a note be made to this effect on the Configure Contribution Page > Title and Settings > Allow individuals to contribute and / or signup for membership on behalf of an organization? checkbox

But I guess the key question is how tricky it is to reset the 'on behalf of' to run on/require a different relationship than 'employee/employer'

Donald Lobo · September 05, 2011, 03:57:30 pm

Quote from: petednz on September 05, 2011, 01:37:22 pm

But I guess the key question is how tricky it is to reset the 'on behalf of' to run on/require a different relationship than 'employee/employer'

Its software, so everything or most things are possible

The relationship defined could be either global or specific to each contribute/membership page. We'll need to store the value in a table etc.

lobo

CiviCRM Community Forums (archive)

News:

Author Topic: Oh behalf of, inherited memberships, and permissions relationships (Read 1161 times)

petednz

Oh behalf of, inherited memberships, and permissions relationships

Donald Lobo

Re: Oh behalf of, inherited memberships, and permissions relationships