Skip to Main Content
IBM Data and AI Ideas Portal for Customers


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Workspace Spectrum Conductor
Components Version 2.5.1
Created by Guest
Created on Jan 31, 2022

More granular control of EGO_SERVICES_CONTROL for notebook consumers

This has been explained with figures in the slack thread: https://ibmsystemslabservices.slack.com/archives/GTDAWABQX/p1643389039169000


Today, in order for a user to be able to start/stop its own notebook in an instance group, the permission EGO_SERVICE_CONTROL is required. However, assigning such a permission to a level in the consumer tree for the Jupyter_6_0_0_ consumer creates the side effect that users can start/stop other users notebooks in the isntance group through the System Services -> Ego Services -> Services entry in the GUI.


The expected behavior requested by this RFE is that a user would only be able to start/stop its own notebook service, not other users notebooks. This could be accomplished by having the GUI itself filter the actions - but doing so would still allow a knowledgeable user to use egosh to do it - or to create a special permission to control notebook services, or some other idea.

Needed By Quarter