Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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

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


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Submitted
Workspace StreamSets
Created by Guest
Created on Dec 11, 2025

The ability to specify RBAC for API credentials and to restrict creation of API credentials

As an admin maintaining StreamSets, I don't want end users to create token on their own without the consent from the admin team. The entire control of creating, managing, deleting the API key should ideally be with the admin team. 

Here, the requirement we have is that one app team already has UI access to the engines of their application (RBAC is defined by us for the same) to create, manage and run their pipelines. Now they want to have a read-only access via API over all the pipelines across all the engines. In this case, if they create an API key, it will have access to only their pipelines (that too with all the privileges and not only read), which is still fine. But if I create an API key and provide the same for them, then it will have all the privileges across all the pipelines since I am an admin. This deviates from my controls as an admin.


 

Needed By Yesterday (Let's go already!)