More security for engagements and KC bots

We have security concerns around engagements and KC bots. We have active users from different departments as well as multiple product lines. Right now, anyone can see and edit anyone else's engagements and KC bots. In the worst case, this can result in accidentally losing content or launching content that isn't ready for public consumption. We'd like to see better access control than the user permissions to manage or launch engagements. Perhaps something similar to the private/share/public settings for reports and dashboards could also be also be applied to authoring/modifying/launching engagements and KC bots?