CiviCRM Community Forums (archive)

In CiviCRM core, permissions for activities is a bit weak: Someone can either see all back-office activities in the system, or none. (E.g. back-office created activities such as "phone call", "meeting", etc.

As a result, I have a quick-and-dirty Drupal module to put granular permissions on activities.  Currently it looks for an activity custom field called "Privacy" which has the options of "Anyone" or "Restricted to a special group".    If the choice of ""Restricted to a special group" is picked, then only users in an ACL group can view/edit that activity.

I would like to change the core and see activity permissions in CiviCRM core, just like "note" and other object permissions are in core.

What architecture should be followed so that this code can be part of the core?   Since the table "civicrm_note" has a field called "privacy", should the same field be added to the table named "civicrm_activity"?

He and I are already working on this together. (as well as the note permissions).  We both wanted more input from the community about planned changes.

Sounds like a good idea to me. Don't want to expend the scope for the sake of it but...

One issue we have had with activities is that the contacts are spread into 3 different tables and the API team would love to have a single activity_contact table with a "role" column in it.

This might be something that would simplify a great lot your implementation too?

X+