CiviCRM Community Forums (archive)

This functionality doesn't currently exist with in the Contact Dashboard, but I'd like to see about getting it made.  Here is the idea:

1) Currently an Individual known as "main person" can have a permission'd relationship with an Org
2) That Org can have a membership will extends to all Individuals who are Employees of that Org

I'd like to add this feature through Contact Dashboard (or thereabouts):

1) "main person" Individual with Permission'd Relationship on Org has ability to Add Individual Contacts through the Contact Dashboard who will
   a) Be assigned as Employees of the "main person"s Org
   b) Be assigned as "subordinates" (for lack of a better term) so that each Employee has a Permission'd relationship with "main person"

2) "main person" can then edit the information of his/her Org as well as his or her subordinate employees

3) "main person" can delete Individual contacts who have an Employee relationship with "main person" Org

Restriction: "main person" need not have more than one Org.  "main person" cannot add or delete Contacts who are not individuals.  "main person" cannot add or delete contacts that are not Employees of the Org

I think there are a lot of people who would enjoy this functionality.  My dream is that it is "done right" by hiring the CiviCRM core team to do it, in a way that is helpful for all who use CiviCRM.  I am willing to chip in $, and hopefully other are out there too!!!

In talking with Lobo he estimates that this effort would take 30 - 50 hours of programming time.  I'd be willing to pony up about 1/2 the cost of the development, if others can fill in the rest let's see if we can make it happen.  Also an wild/wacky alternative might be to make this a "class project" for the Sep 9-10 CiviCRM class in New York, which I am still seeing if I can make it to ($ allowing).

Let me know guys!  Any takers?

I'm afraid I don't understand.  I've already got a situation with my site where I have 2 types of relationships

1) main person > org
2) main person > employee

If both are established when a new contact record is created as a permissioned relationship, then the main person is not "1 level off" as you said, there is direct relationship between the main person and his/her subordinates.  This situation already exists for my site.  I simply also want the main person to be able to add and delete contacts.

So are you saying you don't think it's appropriate or a "value added" to  have this capability ( for "main people" to create contacts for their organization) to be part of CiviCRM funtionality directly?  

Stuart

peterd, thanks.

Just to clarify how I've set up my relationships on my site, which may be redundant or may not, but this is how I did it...

A) 1 Org > Many Employees  Relationship name: Employee/r  (none of these relationships need be permissioned, but could if desired)
B) 1 Main Person > 1 Org  Relationship name: Main person for... (this relationship is a one person per one org permissioned  a>b, so main person can edit org)
C) 1 Main Person > Many Subordinate Individuals (who happen to work at the same Org as the main)  Relationship name: Representative (or possibly could be called 'supervisor') of...

By making C) a permissioned relationship a main can edit all his/her subordinates.  The C) Relationship is established using the "Import Contacts" feature, and made permissioned using a custom MySQL that runs using Cron.

This is all detailed in the documentation (to which peterd kindly provided a link above)...

Ok thanks -- I'm willing to try. 

Just let me clarify then, I'm not actually going to be creating a Drupal module (that uses CiviCRM hooks) then, I'm just going to extend the CiviCRM code itself?

how did you go with this, stoob?