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) »
  • Big association - does CiviCRM fit our needs?
Pages: [1]

Author Topic: Big association - does CiviCRM fit our needs?  (Read 1170 times)

goetzi

  • I’m new here
  • *
  • Posts: 1
  • Karma: 0
Big association - does CiviCRM fit our needs?
February 05, 2009, 09:00:44 am
Hi,

we are a big Austrian non-profit organization and are currently searching for a member management software. CiviCRM sounds (and looks) very interesting but I didn't figure out yet if it can cover all our needs.

Our country-wide organization has 9 sub organizations (one for each state). Each member of one of the state organizations automatically is a member of the "mother organization". 

country-wide organization
|- "child" organization 1
|- "child" organization 2
|- and so on

I didn't find something about nested organizations, is that possible?

We from the "mother" organization should have full access to all members. The people who manage the data in each state should only have access to the data of their state. Can we achieve this with your ACL model?

I found the possibility to import members into CiviCRM. If a state organizaion imports members they should automatically be assigned to the organization. There are no people without membership in the database.

I hope you understand our needs and are looking forward to your replies :)

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Big association - does CiviCRM fit our needs?
February 05, 2009, 10:34:47 am
Several organizations have implemented solutions for similar cases using the ACL hooks functionality that is part of CiviCRM. This approach requires some coding (creating a separate module - if you're using Drupal) which implements the hooks.

There are two components to this:
1. who has permissions to access certain records
2. marking the records by their segment (state in your case)

Core or custom fields are selected to mark each of these. You might have use the core address.state_province field to indicate the state the member belongs to - or a custom field. Your choice will depend on several factors - including whether you need the feature-set that CiviMember provides (tracking membership statuses and fee payment over time).

Then you'll create a "Permissioned For" custom field in a different custom field group (that only certain folks can modify) - which controls access to record sets by state (and includes an ALL value for national level folks).

You can read about some implementations on our blog:
http://civicrm.org/node/381
http://civicrm.org/node/339

... and see some sample code in our SVN repository:
http://svn.civicrm.org/civicrm/branches/v2.2/drupal/civitest.module.sample
civitest_civicrm_aclWhereClause() function
Protect your investment in CiviCRM by  becoming a Member!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Pre-installation Questions (Moderator: Dave Greenberg) »
  • Big association - does CiviCRM fit our needs?

This forum was archived on 2017-11-26.