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,
Post an idea
Upvote ideas that matter most to you
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.
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.