This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
We are facing the need to limit access to certain data columns/fields in LSF Explorer for certain roles.
In our environment a few different teams will make use of the reporting capabilities of LSF Explorer in different scopes. Nevertheless, LSF Explorer is storing sensitive data (e.g. usernames) which are under special attention by local working and privacy laws and agreements in different countries. Hence we have to restrict access to certain sensitive fields to very few persons.
The idea is to do this using several roles (as we are already doing) and to extend the RBAC-mapping with more granularity. So instead of only applying permissions like "report creator" or "report viewer" to roles we would propose to add all data fields to the RBAC settings page to limit or control the data usable for viewing and editing reports.
For the future we can also think of potential use cases to limit access for different users to different reporting capabilities, so this idea is not only limited to user data but to all data fields.
As this is a technical requirement for bringing LSF Explorer in production in a compliant way, there is a huge need and urgency for having this feature implemented.
Please come back for any additional questions or doubts.
Thanks for supporting/considering this RFE as it will support us on using LSF Explorer with our use-cases in a legally compliant way.
Do not place IBM confidential, company confidential, or personal information into any field.