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:

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:

Status Not under consideration
Workspace Product Master
Created by Guest
Created on Jul 19, 2021

Allow role based access of specific hierarchies, specs and lookup tables

Currently different users within our business are able to modify specific hierarchies or attributes. However, just because a user can modify one of those areas does not mean they should be able to access all areas. For example, a marketing user may be able to make changes to the hierarchy used for the ecommerce site, however they should not make changes to the hierarchy used by the merchandising system. Also, a user may need access to change secondary specs but they should not have access to change primary specs.

However, it does not look like we can set up such fine-grained role based access in Product Master at the moment. This means users would have to have access to areas they shouldn't have which could potentially lead to unwanted and detrimental changes happening.

To safeguard our data, configuration and users it would be highly beneficial to be able to specify restricted access to only certain hierarchies, specs and lookup tables. Ideally this would be on the Persona UI so that all maintenance is occurring on one UI only but it would be acceptable to be able to only do it on the Admin UI initially if the eventual roadmap also includes the Persona UI.

Needed By Month
  • Guest
    Oct 5, 2021

    As of now, such kind of features are not asked by any other customer. In case if more customers are interested in such kind of features we can re-evaluate it at later stage however, for now it is not in our roadmap.