Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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 UrbanCode
Categories Deploy
Created by Guest
Created on Mar 20, 2024

Let agents inherit or use permissions and team object mappings from agent pool

Currently, there is no straightforward option to configure permissions purely at the agent pool level. When permissions are set at the agent pool level, they are neither inherited nor used by the agents added to that pool. 

More specifically, when a team member wishes to deploy something, their team needs to be connected to the specific agent on which the deployment will run. If their team is not connected to the agent, the deployment will fail. 

If permissions set on the agent pool could be inherited or used by the agents in the pool, management of permissions across teams and agents would be less cumbersome. Currently, we have to add each of our agents to each of our (many) teams. 

Idea priority High
  • Admin
    Randy Langehennig
    Reply
    |
    May 9, 2024

    Thank you for submitting this idea. We are creating a discussion topic and will review this with our development team. We will be in touch with additional questions or updates soon.