Skip to Main Content
IBM Data and AI RegTech Ideas Portal

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 offering manager 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.

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

Shorter URL for this site is: or

Status Not under consideration
Workspace OpenPages Ideas
Component End User UI
Created by Guest
Created on Jun 30, 2021

Restrict List of Users Returned in User Selector for Filters

If you create a New Filter from the Grid view on an object and choose a User selector field to filter the condition on, all of the Users in the system are available to select. Even OpenPages system users (LEE Users, OpenPagesAdministrator etc) are available to see.

For environments where the access level on user selector fields is set to Read then only Users that can read the object can be seen. This is important in maintaining segregation between the domains of the system.

We would like to see the Filters also respect this otherwise Users have the ability to see User information that they should not have access to.

Needed By Yesterday (Let's go already!)
  • Admin
    JOHN Lundgren
    Sep 27, 2021

    Thank you again for submitting this RFE!

    IBM has considered the request. While we understand the request, it is unlikely to be addressed in the next 18-24 months. If this request receives continued Customer interest, it may be resubmitted for consideration after 18 months from the submit date.

  • Guest
    Jul 1, 2021

    Hi Christophe,

    Yes I think that would work if you could specify the Domain (or Role) that controls it. We have a Library Domain which has shared Read access across multiple unconnected users so it would need to be able to prevent that returning users in the filter.

    Thanks, Adam

  • Guest
    Jul 1, 2021


    If I try to simplify it, If a user builds a pivate filter based on users, he should only see users in the same domain he is. Would that be a simplier way vs access control based?


  • Admin
    JOHN Lundgren
    Jul 1, 2021

    Thank you for submitting this RFE!

    The IBM team is evaluating this RFE. A decision or request for more information will be provided within 90 days of the date that this issue was submitted.