IBM Sterling Ideas

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

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting 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 notifications 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.

Provide the ability to create custom sponsor user types

Provide a way for a sponsor admin to define custom sponsor user types, beyond the current sponsor admin, LOB and standard users.  For the various permissions, there should be a way to indicate what that role can do with each one (nothing, read only, edit/update, etc.).  The IBM Control Center has a nice mechanism for doing this (attaching a screenshot).

The permissions should include things such as which applications can be logged into (portal, repository, provisioner), roll out activities, developing activities, updating e-mail templates, ability to participate in activity tasks based on custom roles, ability to participate in activities regardless of custom roles (current admin privilege), uploading documents, etc.  It should be very granular.

The assignment of a custom user type should be available via the UI along with the current user type options.  The API call to retrieve sponsor users should return all of the permissions assigned.

  • Guest
  • Jan 31 2019
  • Future consideration
How will this idea be used?

This would provide a way to create custom user types to meet business and policy requirements.  This includes segregation of duties, limiting developers to not being able to invite partners, etc.

What is your industry? Banking
What is the idea priority? Urgent
  • Attach files