Hello @Ilan B, thanks a lot for your idea. If I understand correctly you are asking for permissions at the topic level. I have to say, I am a bit afraid this would make permissions way complex.

Thanks for sharing your use case. I'm curious at the different stage of the release of a feature, do you have the exact same communication? 

Thanks @Marion Frecaut.

I get the hesitancy, but I think it should be fine. It obviously should be used with precaution etc, but I imagine users who would use a feature like this to be prepared for the complexities. 

With communication, it’s case by case. However, we do want the documentation to be ready so that Beta users can have all the information in front of them and we can use the same links in our product. This way, when we roll it out, all we have to do is open the article, and from a KnowledgeBase/Community perspective we are ready to go. Otherwise, we would have to hide the article somewhere, and create new links when the feature goes live, and potentially confuse users and lose community value. Yes, I know we can do redirects, but I don’t think that it’s a good practice.

Ilan