Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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 Under review
Workspace Concert Workflows
Created by Guest
Created on May 20, 2026

RBAC to restrict Workflow publish permission for concert workflow users

We are looking to onboard users with permissions that allow them to develop and edit workflows, but restrict them from publishing workflows. Currently, all users have the ability to publish workflows, which is both a security and a cost concern. Additionally, the role management settings do not provide an option to restrict publish/deploy/expose workflow permissions.

We use Concert workflows for multiple customers, where their delivery teams are responsible for creating workflows. Once testing is complete, the admin team is required to publish the workflows via an API endpoint ( which is not possible now ) .

As a workaround, we attempted to remove the Worker permission from the "Everyone" group. However, this caused users to lose the ability to create an API (i.e., they could no longer select a Worker in the API options), while still being able to publish using an existing API. This also had the unintended side effect of preventing users from running workflows altogether.

We have raised a support case for this issue: TS021966501 and its attached. The conclusion of the case is to create a feature request hence creating this

Idea priority High
  • Guest
    May 20, 2026

    case file is attachedÂ