Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
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.

Add idea Subscribe
Status Future consideration
Created by Guest
Created on May 1, 2026

RELATED IDEAS

Prevent network egress at runtime for any authentication endpoint not on the tenant allow list

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?

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

I'll note this is an expansion request on what has already been delivered for connections.

Idea priority Urgent
  • Post comment

By clicking the "Post Comment" or "Add Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not include IBM confidential, company confidential, or personal information in any field.
Having problems accessing this portal? Describe the problems in an email to ideasibm@us.ibm.com.