CiviCRM Community Forums (archive)

Hi Eco - there are a few approaches to this so the answer may not be simple.

One approach is based on 'domain' and you give each sub organisation their own cms front end which you set up with a domain id in the database and hence someone from that cms only sees contacts created via - or deliberately added from the top level to - that cms (and hence having the relevant Domain ID)

The other approach we have worked on and 'like' is based around cascading permissioned relationships.

So if Person A is 'officer' for Branch A, then sees contacts with relationship to Branch A

If Person B is 'officer' for Region A, and if Region A has permission over Branches A1, A2, etc, then Person B has access to all contacts at level A

And up it goes ....

And there may be other approaches other than using the standard ACL Groups approach in core CiviCRM - such as building the ACL to work of the options of a Custom Field - eg Person A has 'A' ticked, Person B has 'B' ticked, and then Manager 'A' can see all 'A's etc

Perhaps if you spell your scenarios ie what makes Contact A have the rights to see Contact B but not Contact C we may be able to point you better to a good solution.