How to add the permission to allow users to change their own reports to global sharing? But at the same time not to delete knowledge object ?

[Hemnaath]

Hi Team,
We got request from a client that he wants users in the test_basic group (role) should be allowed to change his/her reports to global sharing. But at the same time they he do wants the user with test_basic group should not be able to delete the knowledge object of their own app.

I had gone through the below link for enabling a role other than Admin and Power to set permissions and share objects.

http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Manageknowledgeobjectpermissions

But when we give write permission to the test_basic user group, then there is a possibility by the user in this group to delete the Knowledge objects for a specific app (search app) which he has a write permission. So in this case how to restrict this group of user to share the object but not to delete it.

Kindly guide me on this.

[evsmt · Accepted solution]

Define all Knowledge Objects that may not be deleted as .conf files in the /default directory in the app.

This will only work if you know up front which KO may not be deleted. This will not protect against one user deleting a KO of another user which is shared in the app.

[Hemnaath]

thanks for your effort on this, so it means that I can protect only the KO that are present already in that app is that right.

[Hemnaath]

I had followed the below link to achieve this

http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Manageknowledgeobjectpermissions#Enable... text]1

[evsmt]

Yes, this method protects KO's shipped with the app. I do not know of an other method to achieve your goal.