What I would like to accomplish is to have the following. Please let me know if anyone is aware of modules that can accomplish this already or what direction I should take developmentally to accomplish this. Thanks.


All nodes are tagged with terms from a particular vocab through the use of a taxonomy reference field. The nodes are only accessible to specific users that have permissions to view the tagged terms.


I have one vocab that I am working with for all of this control and it is enabled for all content.


All users are tagged with terms from a particular vocab through the use of a taxonomy reference field added to their profiles. This field should only be editable by a certain administrative roles. Additionally, the user will only be able to access content on the site that is tagged with the terms set in this field.

2 Answers 2


Turns out I went with Access by Terms module after finding that the Term Access module did not work for me. Access by Terms also has permissions the make the field editable by certain roles in the profile and nodes, so that takes care of administration requirements too.


As per your requirement you can use Term Access module or its related modules.

From module's project page:

... controls node access based on taxonomy term fields. When the nodes taxonomy terms and the user taxonomy terms match, the user is awarded certain permissions.

  • This does deal with the issues surrounding user access to matching nodes. It does however not cover dealing with the field level permissions that would be needed to keep users from editing the field on their profiles (this should be left to administrators [or really a set of roles]). However, I have opened issue with the field permissions module to see if they will add field level permissions per entity. If they don't I will code a custom module to handle the field level permissions per entity. Awarding to you since the answer takes care of most of the difficulty. Thanks! Commented Feb 21, 2013 at 17:44
  • Actually after testing that module I found that it "simply does nothing" after configuration. I assume there is something busted in code as this is a pretty default install. I switched to drupal.org/project/abt and everything seems to be working. ABT seems to differ as described here: drupal.org/node/1498354 and it works. Commented Feb 21, 2013 at 23:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.