CiviCRM Community Forums (archive)

I'm looking into extending 3.x's ACL capability to solve two specific classes of problems a client has with contribution data.  Short version:  lots of people need access to viewing Activity records, but who donates to the organization and how much is a very sensitive and touchy issue.  In general, people who have EDIT access to a contact should not be able to see donation related information.

So I need to make sure that contribution information is very closely held.  The number of people who are authorized to see donation related information is very small (probably 3 out of hundreds of people who some degree of administrative access), so identifying who should have access is easy.   I believe it's pretty easy to restrict access to contribution records.  But CiviContribute also creates Activity records (this currently is not an option; it just goes ahead and does this), and Activity records don't currently have any way to directly limit access.

Certain, I can (and likely will) override the class that forces the creation of those activity records.  But it would be good for this and other reasons to be able to control view access for Activities.  The natural hook for this would be the activity_type_id, which points to a customizable option list.

What's the best way to add ACL (and ACL-hooks) for Activity records, so that I could do this kind of selection in a clean way?

That looks like it would work.  Thanks.