Answers.Body: <p>I suspect this is because acl permissions is not consistently applied across all aspects of civicrm. In this case the API permission check is a lot more granular.</p>
  
  <p>At this point, I suspect your options are to either live with the status quo and/or (ask your developer if you have one to) take a look at the code to see if you can improve the API to make the permission checking incorporate ACL's also. You can look at the code on the main contact edit page (CRM/Contact/Form/Contact.php) to see how this is done.</p>
  
  <p>You could also consider using the <a href="https://civicrm.org/paid-issue-queue" rel="nofollow">Paid issue queue</a> service offered by the core team if your org has the funding to do so.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-09T02:45:42.970Z
Answers.LastActivityDate: 2015-06-09T20:01:12.920Z
Answers.LastEditDate: 2015-06-09T20:01:12.920Z
Answers.UserDisplayName: Donald Lobo
Body: <p>More specifically, when they click tag checkboxes they get the message "API permission check failed for EntityTag/create call; insufficient permission: require access CiviCRM and edit all contacts". However, they are able to tag users after clicking the "Edit" button.</p>
  
  <p>The solution offered by the error message (enabling, in Drupal, the ability to edit all contacts) is not practical for me since it also allows them to view all contacts (which is against our internal policy).</p>
  
  <p>A little more info on my permission structure in case it's relevant: My ACLs allow users to view and edit contacts that are members of certain groups. Ex: A user named "Bob" is in the group named "Staff". Those in the group named "Staff" are allowed to view and edit contacts in the group named "Universe". </p>
  
  <p>As admin, I don't have this problem. But when I log in as a lowly user I do.</p>
  
  <p>Drupal version: 7.37. CiviCRM version: 4.6.3. Thanks in advance for any help.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-23T16:01:41.097Z
Comments.Text: Note: Error persists in 4.6.8.
Comments.UserDisplayName: Eric H
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-10-05T23:12:21.323Z
Comments.Text: I have the exact same situation with CiviCRM 4.5.8 and Wordpress. The non-administrator is getting the error: "Sorry an error occurred and your information was not saved". This is a serious problem. I was so happy when ACL permissioning started to work and now...what good is it? I have to make everyone Admins? We're all volunteers. We don't have much money. Will $100 help?
Comments.UserDisplayName: jimcrist
Tags: <permissions><acl><tags>
Title: Non-administrators unable to tag contacts using Tags tab
ThreadText: # Non-administrators unable to tag contacts using Tags tab
  
  (Asked by: username_0 on 2015-06-05)
  
  More specifically, when they click tag checkboxes they get the message "API permission check failed for EntityTag/create call; insufficient permission: require access CiviCRM and edit all contacts". However, they are able to tag users after clicking the "Edit" button.
  
  The solution offered by the error message (enabling, in Drupal, the ability to edit all contacts) is not practical for me since it also allows them to view all contacts (which is against our internal policy).
  
  A little more info on my permission structure in case it's relevant: My ACLs allow users to view and edit contacts that are members of certain groups. Ex: A user named "Bob" is in the group named "Staff". Those in the group named "Staff" are allowed to view and edit contacts in the group named "Universe".
  
  As admin, I don't have this problem. But when I log in as a lowly user I do.
  
  Drupal version: 7.37. CiviCRM version: 4.6.3. Thanks in advance for any help.
  
  **Tags:** permissions, acl, tags
  
  > **Comments:**
  > **username_0**: Note: Error persists in 4.6.8.  
  > **username_1**: I have the exact same situation with CiviCRM 4.5.8 and Wordpress. The non-administrator is getting the error: "Sorry an error occurred and your information was not saved". This is a serious problem. I was so happy when ACL permissioning started to work and now...what good is it? I have to make everyone Admins? We're all volunteers. We don't have much money. Will $100 help?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-06-09. Score: 3
  
  I suspect this is because acl permissions is not consistently applied across all aspects of civicrm. In this case the API permission check is a lot more granular.
  
  At this point, I suspect your options are to either live with the status quo and/or (ask your developer if you have one to) take a look at the code to see if you can improve the API to make the permission checking incorporate ACL's also. You can look at the code on the main contact edit page (CRM/Contact/Form/Contact.php) to see how this is done.
  
  You could also consider using the [Paid issue queue](https://civicrm.org/paid-issue-queue) service offered by the core team if your org has the funding to do so.
  
  
  ---
  
  