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 Cloud Pak for Data
Created by Guest
Created on Jul 9, 2021

Provide use case level authorization in addition to the existing user level authorization

The idea is a use case related authorization to provide a more fine granular means than the current user based authorization. What we are looking for is that for each user the Active Directory will maintain a list of use cases the users are allowed to work on. Before the users log on to CP4D they decide to work on which use case they want to work on. He approves the use in an company own rights management system which shares the information in an extra LDAP field. They should then only be authorized to work with the resources authorized for this use case.


Effectively this would be an authorization scenario. The goal is to use additional fields in the Active Directory, where the use cases are specified and based on this information access to certain resources the user has access to will be granted/denied.
So consequently this will have to be configured on resources within Cloud Pak for Data.

Example: User A is allowed to work with Catalog X but also with Catalog Y. However they also want to specify that Catalog X should only be worked with for Use Case 1 and Catalog Y for Use Case 2. When the user logs on they decide on the use case they want to work on and have only access to the so specified resources.
A use case could be self service analytics for health in-patient care or self service analytics for out-patient care. If they log on to the in-patient care use case, they want to only see the resources dedicated to in-patient care, not the out-patient care resources in order to prevent unwanted changes or usage from happening.

The key here is that it is the same person that can work on either of both use cases, but the concerns are kept as separated as possible in order to prevent accidental misuse of the wrong data assets or governance artifacts.
The Active Directory would provide the information about the use case and CP4D would have to map that to access rights.


Maybe this feature can be selectively enabled/disabled through the LDAP configuration page

Needed By Yesterday (Let's go already!)
  • Guest
    Jul 20, 2021

    A traditional Mexican hammock has no spreader bars so to keep the hammock open and not end up wrapped up like a taco you lie diagonally or across the hammock. You become the "spreader" and the hammock rolls along beneath you, hugging and supporting every curve of your body!

  • Admin
    Yalon Gordon
    Jul 9, 2021

    This use case should be handled by Attribute Based Access Control (ABAC) -- enviornment variables (catalog X, Y) and use case variables (use case 1, 2). It's on our roadmap but not currently committed.