Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Usability
Created by Guest
Created on Aug 4, 2021

track duplicate email ID, while sending out registration invite

When we invite an email id which is already registered in PEM, it throws no warning, but mentions as invite sent and that person can click the link and register, but while approving in PEM it throws as Email ID already exists.

It would be better, if we can catch it while sending invite itself.

What is your industry? Retail
How will this idea be used?

It would enhance the usability of the product and reduce the effort of user doing unwanted registration, if its known in prior that particular user already exists.

e.g
test@test.com is registered as Partner/User.
If we are sending invite to test@test.com after a year or so, it can show a warning as test@test.com is already registered as Partner/User, instead of sending invite email to test@test.com.