Deployment Architecture

How to prevent users taking clones of knowledge objects?

mbasharat
Builder

Hi,

I am dealing with a situation where many users in Production are taking clones of knowledge objects e.g. scheduled reports, views etc. How to prevent this? Any settings in the configurations and roles capabilities I can apply to prevent this? Our configuration settings for access controls has read only for users. Write is for developers and admins only. This still does not prevent users from taking clones.

Thanks in advance!!!

0 Karma

richgalloway
SplunkTrust
SplunkTrust

What is the problem with cloning knowledge objects?  Is it possible users find the existing KOs inadequate and are creating better, private instances of them?

---
If this reply helps you, Karma would be appreciated.
0 Karma

mbasharat
Builder

Hi Rich,

The issue is that users are creating clones of KOs and due to the lack of their training and knowledge, they try tweaking the cloned KOs in an un-optimized manner which is causing heavy load on infrastructure. We are asked by management to shutdown the cloning for users with read only access so they are unable to take clones to begin with. Thanks.

0 Karma
Get Updates on the Splunk Community!

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...

Splunk App Developers | .conf25 Recap & What’s Next

If you stopped by the Builder Bar at .conf25 this year, thank you! The retro tech beer garden vibes were ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...