Alan Colon: I'm not sure I follow. Requiring authorization to apply to certain tags is what I'm asking for. I want certain groups to only be able to access pages with certain tags. ie guests can only access pages tagged "public", players can only access pages tagged "player" or "public", and so on. Having rules tied to paths is not ideal because if I want to change access later on for a specific page I need to change the path which breaks any links associated with that page. My goal is as follows. First I create a new page which is a draft and doesn't have any tags, it is only accessible to the admin group. Once the page is complete then I'd give it it's tags. I tag that page player so that everyone in the players group can see it. Later on the page needs to become public so I tag it as such and it becomes visible to anyone that visits my wiki. I've edited my original post as that should have said "inaccessible to guest users by default". Hope that clears up what I'm asking.

I'm planning to use my wiki to manage my Dungeons and Dragons campaign setting and campaign info. I want to be able to create all new pages as rough drafts that only I can see, for this I'm actually fine with putting all new pages in /draft/ and moving them when complete. Once completed if the page contains general setting info I would tag it "public" so anyone could see the page. Each group of players that I run sessions for will have information that only those groups should see, this information will often become public though after a session. Therefore I would want a user group for each group of players and an appropriate tag to enforce what they can see, once a page should become public I just give it the tag. This can currently be accomplished using the path based rules but if I want to change access to content then I need to change the path and any links to that content are broken. The path based rules are going to be problematic for anyone with a use case where they want to change access to pages throughout the page's lifetime.

I think what Alan means is that anyone with edit access can set tags for a page right now. It would be nice to define tags in the permissions page that only specific groups can assign to pages.

Naser Abdelrahman: Thanks for clearing that up! Now it makes sense. I don't think this would be too much of an issue though if it is at all. If a user does not have access to edit a page then they can't modify tags. I can still see Alan Colon's point, but for my use case that wouldn't matter. I would only be giving page edit permissions to trusted sources.