Hi there! We are using Insided heavily to host our product Knowledge Base, as well as creating the community around this to encourage self-serve.

Our support team has an internal knowledge base on Notion, but we want to migrate this to an internal, hidden section within Insided… however we have hit some roadblocks and wonder how others have managed this.

We have experimented with a few different approaches, none of which have a perfect outcome:

1. Hidden Community section → it’s not possible to manage Parent Category visibility settings by user role, but we discovered that if all child categories of a Parent Category are invisible to you, then you won’t see the Parent Category (we found the visibility here a little inconsistent - it’s not clear if tihs is intentional or a happy accident).
   1. The major problem with this approach is that even if you can’t see the category, the category option appears in other Community sections when creating a Question (so customers would see an option to post it to an invisible section called ie Internal Support KB)
   2. The benefit of this approach is that we don’t need Admin/ Moderator licenses for everyone on the support team to be able to contribute things like Questions/ Conversations to the internal Support KB.
2. Hidden KB Section → using the similar method of visibility as above, this means we don’t have the issue of the visible category options for customers… however it’s not appropriate for all of our support team to need Control Panel access to our Community. 
3. Hidden Group → this would work well, except we cannot sub-categories topics within a group so it becomes harder to navigate as the Support KB grows. 

Curious if anyone else has tackled this?