Toby Thanks for the explanation.
I'm thinking of my current esoTalk site as a sample use case. We've set up nested forums in such a way that access is gradually restricted in some cases. For example, we've got these two forums:
- Site Development
- Event Planning
And we've got two user groups, Site Team and the Events Team. The Site Team can access stuff in both of the above forums, but the Events Team can only access stuff in the Event Planning forum. Now, that forum is further subdivided into the following sub-forums.
- Event Proposals
- Event Menu
- Event Preparation
- Event Feedback
Anyone who belongs to either of the two groups can access stuff in the Proposals and Feedback sub-forums, but the other two are restricted. You need to be a member of a third group (Event Leaders) to post anything in the Event Menu sub-forum. And only members of the Event Leaders group can start a thread in Event Preparation, but anyone can see a thread in that forum can respond to it.
There's much more to it, but that gives you the general idea.
Since Flarum allows nesting of tags, we can use that functionality to organize information in something approaching what we've done with our esoTalk site. At least, close enough for jazz. However, your description of the permissions makes it sound as if we'd have a hard time restricting permissions gradually the further you go in.
@Kulga makes some very good points, but from the standpoint of giving admins maximum flexibility with a minimum of configuration, it might be a good idea to AND the permissions on tags rather than OR them as the default behavior.