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 Not under consideration
Created by Guest
Created on Oct 30, 2018

Modify security model of IGC Catalog permissions

Reference this support case: https://www.ibm.com/mysupport/s/case/5000z00001H5vkDAAR/problem-with-catalog-permissions-in-igc-115

We are currently attempting to implement a security model for Information Governance Catalog (IGC). The security model we would like to implement needs to take into account that our system supports multiple businesses. I plan to implement the model by using Catalog permissions, creating a top level category per business and allow appropriate access based on restricting access to certain groups.
We would like all users across all the businesses to be allowed read access to the entire repository so that all businesses can read all categories and terms for every business we support.
Additionally we would like author/s from each business to be allowed write access only to the categories that they own.
Plan is to create a group which has only IGC Basic User (effectively read-only) access, lets call it RO-Group.
Also plan another set of groups, each with Information Governance Catalog Glossary Author (effectively read-write) access (RW-Group-Business), one for each top level category.
Category permissions config to be as follows:
1) Every top level category allows access to RO-Group
2) Each top level category allows access to the group with Author access for that category e.g. Top Level Category A allows access to RW-Group-BusinessA, Top Level Category B allows access to RW-Group-BusinessB etc

My preliminary testing shows that if a user is in both RO-Group and RW-Group-BusinessA, and RO-Group is granted permission to access Top level Category B, then the user is able to edit details in Top level Category A as expected but also allowed to edit Top level Category B, which is not what we want.
It's as if access is granted to a category based on whether a user is part of a group that has any level of access, and level of access is determined by the maximum level of access a user has given the groups he is part of, irrespective of whether the higher level access group is allowed access to the category.

Support has advised that this is a current limitation of the IGC access model and suggested raising a RFE to support our requirement. So, in short RFE is to enhance IGC Catalog permissions such that level of access a user has to a category is determined by the maximum level of access of groups which are allowed access to the category.