Our organization will easily have hundreds of K2 Categories due to the level of integration with SharePoint. That said each of these K2 Categories will have unique permissions. As of K2 5.2 the setting of these K2 Category permissions is a manual task. Example - the K2 Security Admin would have to browse to the specific K2 Category, break inheritance, remove the Everyone Role and add the necessary SharePoint Security Groups. We have worked with K2 and they have developed for us a console application to address this scenario. While this console application is meeting our requirements the goal would be to have this functionality be part of the base K2 product.