Body: <p>Two of my clients would like to be able to restrict the contacts that can be assigned to an activity.  This is because they handle highly sensitive information and it would be potentially disastrous for them to accidentally select the wrong contact (e.g. a client rather than a case worker).  This was asked before <a href="https://civicrm.stackexchange.com/questions/7839/restrict-contacts-available-to-be-assigned-to-an-activity">here</a> and the question was rated a 5 - the answer from Coleman was to make a code change. I think there's a good case to build some kind of configurable restriction into core. So I'm asking this question again to see how much support there is for a core update, or alternatively to see if anyone has a better idea.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-15T22:24:15.073Z
Comments.Text: What CMS? Asking, as i did on the other ticket, because Drupal already offers this via webform_civicrm
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-15T22:26:34.657Z
Comments.Text: actually if you are really asking the same question again then you may find this gets deleted as a Duplicate and you would do better to engage on the original one
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-16T08:14:27.420Z
Comments.Text: The problem is that the original answer isn't satisfactory - so all I can do there is add a comment which will have less visibility. A weakness of this Q&A approach, I guess, and where the old forum worked better.
Comments.UserDisplayName: Andy Clark
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-16T10:28:37.483Z
Comments.Text: There's usually not much appetite to put something in core if it can be easily done with an extension.  The basic mechanism exists via a hook (see other answer) so it needs a configuration screen to determine which activity contacts need to be restricted.  Sounds like a fairly straightforward extension.  Commissions welcome :-)
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-11-16T19:35:47.690Z
Comments.Text: Understood re the Q+A format. If you tweak your question to more clearly differentiate it then happy to remove the duplicate flag. But also worth making a comment on the other one since that has eyeballs on it. The fact 5 folk have given Coleman's answer a +1 doesn't mean much more than 5 folk saw that he had made an effort to respond in an informative way and no other Answers had been offered to compare with.
Comments.UserDisplayName: petednz - fuzion
Tags: <activities>
Title: How to restrict contacts that can be assigned to an activity?
ThreadText: # How to restrict contacts that can be assigned to an activity?
  
  (Asked by: username_0 on 2018-11-15)
  
  Two of my clients would like to be able to restrict the contacts that can be assigned to an activity. This is because they handle highly sensitive information and it would be potentially disastrous for them to accidentally select the wrong contact (e.g. a client rather than a case worker). This was asked before [here](https://civicrm.stackexchange.com/questions/7839/restrict-contacts-available-to-be-assigned-to-an-activity) and the question was rated a 5 - the answer from Coleman was to make a code change. I think there's a good case to build some kind of configurable restriction into core. So I'm asking this question again to see how much support there is for a core update, or alternatively to see if anyone has a better idea.
  
  **Tags:** activities
  
  > **Comments:**
  > **username_1**: What CMS? Asking, as i did on the other ticket, because Drupal already offers this via webform_civicrm  
  > **username_1**: actually if you are really asking the same question again then you may find this gets deleted as a Duplicate and you would do better to engage on the original one  
  > **username_0**: The problem is that the original answer isn't satisfactory - so all I can do there is add a comment which will have less visibility. A weakness of this Q&A approach, I guess, and where the old forum worked better.  
  > **username_2**: There's usually not much appetite to put something in core if it can be easily done with an extension.  The basic mechanism exists via a hook (see other answer) so it needs a configuration screen to determine which activity contacts need to be restricted.  Sounds like a fairly straightforward extension.  Commissions welcome :-)  
  > **username_1**: Understood re the Q+A format. If you tweak your question to more clearly differentiate it then happy to remove the duplicate flag. But also worth making a comment on the other one since that has eyeballs on it. The fact 5 folk have given Coleman's answer a +1 doesn't mean much more than 5 folk saw that he had made an effort to respond in an informative way and no other Answers had been offered to compare with.  
  
  ---
  
  ## 0 answers
  
  