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 Delivered
Created by Guest
Created on Aug 29, 2025

Outbound access policy configuration to control which API endpoints agents/tools can access

In industries with elevated compliance & security requirements there is often a need for multi-layered security.

Currently Orchestrate's security model makes the assumption that the builder role is fully trusted.

What happens if a builder through either malicious intent or error creates a tool & establishes a connection to an unauthorised API endpoint?

With auditing of events we can see after the fact what happened, however currently there is nothing to prevent this from occurring.

Idea is for implementing some form of policy based control to agents/tools/connections so that they can only connect to API endpoints (hostname, IP address, port, etc) on an allow-list maintained by an admin role.

Idea priority Urgent
2 MERGED

Restrict what endpoints a tenant is able connect with

Merged
Admins need a way to manage which external URLs or APIs agents can access. The ability to approve outbound connections would make it easier to keep integrations secure and compliant with company policies while still getting the benefits of SaaS.
6 months ago in IBM watsonx Orchestrate Delivered
2 MERGED

Restrict API access by role / network access

Merged
Organizations need the ability to restrict API access based on defined roles and network policies. Allowing teams to limit who can invoke specific APIs—and from which IP addresses—would strengthen security, prevent unauthorized use, and ensure tha...
6 months ago in IBM watsonx Orchestrate Delivered