Forum container permissions vs. forum permissions.

With Drupal 4.7.0-beta3 and TAX 4.7.0 you can enable certain people to view, some others to change and still other people to delete and update in specific forums. There is, however, a small 'trick'/bug/feature involved if some of the forums are placed within a container. For instance.

Announcements (short: A)
-- Board announcements (B)
-- Committee announcements (C)
-- Discussions (D)

Within the category permissions in the access control pages, this will result in an additional row of boxes for the container A.

Now, if user X needs Create permissions in, for instance, C, then only checking/activating the box for C under Create is not enough to grant create permission. One also needs to activate/check the Create permission for container A. If this is not done, then the C forum will not appear in the dropdown list to select a forum for posting a new topic.

I'm not sure if this is bug or feature, but IMHO I consider it not appropriate. A container doesn't directly involve content so why display checkboxes for containers at all? It doesn't make sense to have Create permission in a container (in which nothing can be created).

Ok, [after a minute of thinking], I can see that the View permission is an easy way to not allow viewing for all forums in a specific container. Along the same lines for the other permissions. But if this then is a feature/by design, then it should be documented somewhere. At least I wasn't able to this tip anywhere.