Getting started

For you use case the Private module would seem to be a simpler choice.

Documentation is at: http://drupal.org/node/31601

Some examples are at: http://drupal.org/node/1313460

This module took me days to understand, but it's a good one once you get it.

Here is the document I created for myself so the next time, I won't have to start all over again.

Drupal 7.23

Taxonomy Access Control from scratch

Create roles:
For example: Public, Private, Parents, Coaches, Kids, etc.

Add “Access Level” taxonomy vocabulary:
Add terms to that vocabulary that are clear references to the roles you just created.
For example: Public, Private, Parents, Coaches, Kids, etc.

On each content type:
Add “Access Level” field with term reference and term_reference:access_level (something like that) select checkboxes or list, this doesn’t matter.
On field properties page, change the number of values to unlimited (a lower number may be a wiser choice, depends on how your roles are set up) and select “Access Level” as the vocabulary. You can also set the default access to “Public,” this is optional but it means all pages are by default, publicly accessible unless specifically set to "Private" or some other vocabulary that you just created.
Go to manage display and hide the term reference field and hide the link

On each node:
Edit and select the access level that you want to have permission to this item.

Go to Taxonomy Access Control:
Edit anonymous users and add each of the roles you created. Click arrow select list under "Access Level"
Give them deny for everything but Public, where you can give them A, I, I
Continue with all other roles and deny, deny, deny!

Do the same for the other roles, just giving them access to the appropriate vocabulary term.

Once everything is set up, you will need to go back to previously created content and apply the appropriate taxonomy term by selecting it on the basic edit page.

From now on, when you create content, you can select which group has access to it by selecting them on the basic node edit page. Remember, we set the default to be "Public" so just be aware of that.

It's easy for me to say it, now I just need to figure out what I'm missing setting up TAC for the forums.
Can't get that to work to save my life, and that's why I needed this module in the first place!

Just figured out my troubles with setting TAC up with forums.
Make certain when you add their permissions that you put a check in "View Tag."

That was probably obvious to everyone but myself, but I didn't see it mentioned anywhere.

Worth noting that even if your taxonomy is set up and applied to existing content before installing this module, you will still need to go back and save that content once you have set up Taxonomy Access or its permissions won't get generated.

Also worth noting that you probably should use the latest dev version if you are not totally opposed to using dev versions, it has an extra 2 years worth of bug fixes and enhancements.

@derbexuk:
I have never had to go an resave content in those situations.

Instead, if you have issues with content permissions go to the status report page (admin/reports/status) and click the "Rebuild permissions" link in the "Node Access Permissions" section.

The only time I generally have issues with that though is when I add or remove a content access realted module, not just from changing config.

Also, the dev version has slightly better help text than the current recommended release at admin/help/taxonomy_access

Is there any reason blocking another tagged release?
The last commit is over two years ago.