CiviCRM Community Forums (archive)

Hi all, I'm looking for help from this community to see if the problem I'm facing is similar to what you folks may have experienced as well.

My understanding is Contact module is core to a CiviCRM install and the idea is that most information from contact view would be available to most users who have permission to view contacts. I'm trying to setup only some groups to have access to some tabs from Contact Page like Relationships and Activities (call log, meetings, compose email, etc). I don't know if it is possible to do this through profiles.

For example, let's say I call one of my members and s/he complains about a customer representative, or maybe there is a suggestion or even an issue that should be treated as confidential. Do you know if there is a way to set the permission so only some people (like one supervisor from customer service or a psychologist, priest, etc) would have full visibility to the information entered/stored on these forms?

Thanks in advance!

regards,
Kleber

I've added a "feature candidate" for this on the 2.2 roadmap. The current implementation for controlling access to these contact "tabs" is a bit inconsistent as you can hide "component-related" tabs (at least in Drupal installs) by modifying the "access CiviContribute", "access CiviEvent", etc. permissions. However - you can't control Activities, Relationships, Groups, Tags and Notes as of yet.

you can modify the code at:

CRM/Contact/Page/View/Tabbed.php, line 278 or so

u'll need to unset the array entries for the tabs you dont want the user to see. You might be able to do this earlier on in the process also

ping us on IRC if u need help or have any questions (http://embed.mibbit.com/?server=irc.freenode.net&channel=%23civicrm&forcePrompt=true)

lobo

In CRM_Contact_Page_View_Tabbed::view(), we call hook_civicrm_links() to bring in other tabs that may be produced by a module.

One solution here would be to key the returned array, and allow for modules to remove tabs via the same hook.

This allows module authors to cleanly remove tabs using an external system (eg: we have a custom data tab which should only be visible to site administrators).

Currently, if an external module adds a separate tab with a matching ID, Dōjō throws an exception: "Error: Tried to register widget with id==custom_19 but that id is already registered".

I've implemented part of this, namely the ability to remove tabs, but it's still possible for a user who has access the right "access all custom data" to access the custom data group URL directly and edit the data.

I'd be interested to look at ways in which module authors can interact with CiviCRM to add custom permissions hooks to restrict access to URLs.

In Drupal space, the same hook provides the facility to add/remove menu entries (including subtabs) and the permissions to access the generated URL.

I think the implementation attached below could be cleaned up (eg, assigning blank params to remove an entry is a bit messy), but it functions OK.

Drupal's hooks are additive, but allow you to "add" entries over the top of existing entries, and I think this is a good model (maybe because it's familiar, but also because it prevents having a second pass through a hook function).

To remove an existing entry,

function mymodule_menu($may_cache) {
  $items[] = array(
    'path'     => 'path/of/existing/entry',            // path to remove from menu
    'title'    => 'This text will not appear anyway',  // label won't be visible
    'callback' => 'drupal_not_found',                  // return drupal 404 for this path
    'type'     => MENU_CALLBACK,                       // don't show an entry in the menus
  ) ;
  return $items ;
}