Skip to Main Content
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.

Status Future consideration
Created by Guest
Created on Nov 21, 2025

Ability to restrict access to users by IP address on AWS

Customers need the ability in AWS to specify (allow list) IP Address ranges (CIDRs) from which their tenants can be accessed. We do this in IBM Cloud via IAM/Account IP Address restrictions. We need to implement this in AWS.

This is a common enterprise requirement so that customers can ensure that their users and applications are only connecting to WXO from known environments. This prevents their users from connecting via unapproved devices and also prevents their users' creds or their API Keys from being used by anyone on the internet from who might obtain them via a security breach, phishing, bad actors scenarios for internal users, etc.