Skip to Main Content
Integration


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.


Status Planned for future release
Created by Guest
Created on Sep 12, 2025

Custom privileges for Custom roles for users in the Integration SaaS

Integration platform has only two default roles: "Admin" and "Developer" (notice that there is no "Oper" role).

We are sharing the platform with other teams and we provide them access. But they SHOULD NOT BE ABLE TO SEE, EDIT, DELETE or PUBLISH projects that don't belong to them. Therefore we create "custom roles" and limit their visibility only to a few projects that they own. We assign this role to new users (depending on the team they are coming from) and we remove the "Developer" role, so they cannot alter/interfere with other business units.

The problem: a user with a custom role CANNOT PUBLISH THE PROJECTS with WRITE (or total) access in his custom role.  We need them to be able to publish.

So either we (the admins of the platform) publish somebody else's work (without having complete knowledge of what it does, be available at off hours, etc) or we give them access to projects that they should not see (because they have higher level of confidentiality, security, availability, criticality, etc.)

Is there any way you can allow admins to grant "Publish" or other type of privileges to users that have custom roles and not "Developer" nor "Admin"?
Meanwhile, you are doing that, would you be able to allow "Admins" to remove privileges from default "Developer" role to make it more restricitve? Or could we create a new one with more restrictions and set it  as default? The more complex solution would be to create "Provider Organizations" and projects should be inside them, just like Catalogs exist in API Connect Provider Orgs. Take some inspiration from APIC. 

Thank you, 
Best regards.
 

Idea priority High