Restrict knowledge admins to edit publish etc on other KB

[GM5]

Hello all,

I have the following requirement, basically we need a role to allow specific users to edit, retire, update, publish, republish(publish retired articles), currently the knowledge_admin does this, but this also allows users who have this role to do the same on other Knowledge base articles even if they don't belong to the list of managers it also display ALL Knowledge bases we want to keep the visibility by User criteria and it appears that his role ignore this, is there any way to do this without creating a new role and new ACLS?

I've been  checking these articles

https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/product/knowledge-management/conce...

https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/product/knowledge-management/refer...

[SebastianKunzke]

Did you try to use the knowledge_manager role? This should enable only the managers of the knowledge base to perform this actions. 

[GM5]

Yes, we did but users still need to Republish retired articles, for this part we can override the "canRepublish()" method using the KBKnowledge() script include which is an extension of KBknowledgeSNC by adding a custom function and make it work like we want (e.g to show also Republish for members of the Managers field on the KB definition) but yet we still have the issue that knowledge_manager can see other kb article records from other Knowledge bases and is able to click on Checkout, we wanted to see if there's an OOTB way to do this rather than modifying ACLS, modifying UI actions and using overriding script includes.

[SebastianKunzke]

Sorry, yes, the republishing is not possible for knowledge managers. In this case you need to modify the OOTB process or review, why you need this feature so often. Because an alternative way would be, that you use the insert and stay function to create a new knowledge article. For sure the versioning and other steps would start again, but this would work out of the box.