Bear in mind that, like all modules which use Drupal's built-in node_access features, this module does not prevent users from viewing/editing nodes which Drupal's permission allow them to view/edit. To use, configure Drupal to not grant the permission, then configure tac_lite to grant via the node_access table.
Seems to have a couple of problems.
Trigger for auto publish by moderator does not work, really.
At first sight, you may think it's just another fork of already available module on drupal.org like taxonomy_access or tac_lite. First one is a taxonomy control access based on roles, second one is a taxonomy control access based on users. But both of those modules miss the - according to me essential - inheritance notion :
if you have access to one term, you don't automatically have access to the children nodes. My module does take care about inheritance and this way permit a powerfull user access control.
an economic critique
4.Select the content types to which your workflow will apply. If you want moderators to be able to deal with all content types create a single workflow. if you don't want roles that deal with one content type, say page, to see content that is being handled exclusively by another role, say blogs, then it's usually best to create separate, but near-identical, workflows, one per content type.
5.Press the workflow's Edit link (/admin/build/workflow/edit/1) to define which roles may invoke which workflow state transitions. You may want to start with this:
This Manager is intended to be an aid to help me to stay focused on projects and priorities. These are really nothing more than notes to myself. The act of building this Manager alone forces me to develop and maintain skills required for working with Dreamweaver CS4, which is not a trivial task in its own right.