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?
More security for engagements and KC bots
PX Admin & Security
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
This is also related to