Skip to Main Content
Integration
Hide about this portal


This is an IBM Automation portal for Integration products. 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.


Support subscriber teams/groups and shared subscriptions for EEM / EEM UI

See this idea on ideas.ibm.com

Today a subscription to an EEM Option is bound to a specific person that was working for a specific project, which is a subscriber system. Once that person leaves the project or company, someone else has no access to the subscription and also the contact information (contact email) in the EEM registry is outdated. Today, likely a new member of the subscriber project needs to subscribe for the same topic/option again and the system has to rotate the credentials, which is admin effort and maybe downtime (especially taking over the offsets of the previous credentials). Our customer today is using OneAPI for sync REST service management (likely similar to API connect). There, a team/group can be created with multiple persons being member of the team/group. The subscription is not owned by an individual but by the who team/group. Therefore, if some team member is leaving the team, a new team member can just be added and there is no need to redo any subscription or issue new credentials.     

Idea priority Urgent