What: While it is possible to publish content in categories that are either visible to all or hidden to some which enables defining content permissions, it is not possible to have a category with topics of different permission levels.
This means that we are having to compromise the use of categories for structuring in order to use that same lever for permissions handling. This has surely been mentioned before but I failed to find it…
Context: I’ve been pitching moving our Knowledge base to InSided recently, or at least through a content integration have the KB front end be the community platform instead of a standalone site. (We already have federated search but because our users know where to find the KB already they go directly there, missing the opportunity to search both resources).
When exploring the conversion possibilities it became very obvious that setting permissions only via Categories was a compromise to the more natural use of categories: Structure. So KB content that we want to make public would have to be placed in a separate category and therefore be removed from the category it belongs to, or duplicated to appear in 2 categories which is not efficient.
cc
