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 »
  • Pre-installation Questions (Moderator: Dave Greenberg) »
  • "Employee Of" membership inheritence and privacy setup best practices?
Pages: [1]

Author Topic: "Employee Of" membership inheritence and privacy setup best practices?  (Read 1279 times)

Sky

  • I’m new here
  • *
  • Posts: 6
  • Karma: 0
  • CiviCRM version: Focusing on 4 w/ D7
  • CMS version: Drupal 7
  • MySQL version: 5.1
  • PHP version: 5
"Employee Of" membership inheritence and privacy setup best practices?
February 24, 2011, 07:32:48 pm
Hello,

I would like to set it up so the person that signs up their organization for an institutional membership would setup themselves and optionally others as membership maintainers, and then add other individuals with the "employee of" relationships to grant other employees membership privileges (these would get Drupal accounts with member only access for example)

The concern I have is how to balance the power of duplicate detection in CiviCRM upon creating a new user with not exposing private data of existing user accounts.  Does this make sense?  Are there instructions on how this can be setup that would hold an auditor's scrutiny?

Thanks
Sky

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Pre-installation Questions (Moderator: Dave Greenberg) »
  • "Employee Of" membership inheritence and privacy setup best practices?

This forum was archived on 2017-11-26.