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: http://ibm.biz/WFS-Ideas or https://ibm.biz/RegTech-Ideas

Status Under review
Workspace IBM Safer Payments
Component Operational
Created by Guest
Created on Mar 30, 2022

User Management as a Roles Permission

Move User Management Privileges from Global Privileges to a Role permission.

Currently, user management is permissioned via a global privilege on a user's account. When the "user accounts" privilege is set to "change," the user can view and edit all user accounts permissioned at the same mandator and lower mandators. We want this moved to a role level permission, with additional abilities to specify which level of users should be editable.

We have some users (User Type A) who need access to edit user accounts in lower mandators (User Type B), but who should not have access to user accounts in the top mandator (User Type C) nor in the same mandator (User Type A). To work around this, we have set up User Type A in the second level mandator. User Type A users can access the user accounts for User Type B as needed, but they also have access to User Type A accounts, which we do not want them to access.

In addition, User Type A needs access to batch jobs and audit logs. These permissions are only available if the user is defined at the top level mandator. We cannot set up User Type A at the top level mandator as they would have access to edit all user profiles A, B, and C.

We propose moving the User Management privileges to a role definition. This way we could set up User Type A in the top level mandator, allowing them to access batch jobs and audit logs. We could then use roles to permission these users to edit users built at lower level mandators only.

Needed By Yesterday (Let's go already!)