IBM Watson Data & AI - Structured Ideas

This Ideas portal is being closed.  Please enter new idea at

DSXL: Locking down the production environment to regulate which environment is used as a production

Whilst customer want to have dynamic environments for the data scientists to install packages/libraries whilst "experimenting" customer want to lock down their production environment. So that is going to be possible to have an environment where only the Admin can install packages at an environment level and therefore make it so that if a user runs a notebook which tries to install a new/updated library this will fail? This means customer can keep a solid grip on the production environment and just have a policy that whilst people can experiment with whatever environments they like, if it is going to production then it has to conform to "environment X".

  • Katarina Gašperlin
  • Dec 14 2018
  • Needs review
Customer Name
Role Summary
  • Attach files