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 Apr 21, 2026

Workspaces connections and credentials are restricted to a given private workspace

In order to prevent users from changing connection details associated with an agent in a private workspace, only member of the private workspace can see the associated connections and credentials.

Additionally, different teams using wxO will need to configure team credentials differently, especially when using an out of the box tool or something from the catalog. Segmenting these connections and creds by teams/workspaces.

Additionally, some teams may be working with a DB connection with sensitive data, and they need to ensure other teams in other workspaces cannot access or reuse these connections details

Additionally, one team using an MCP gateway and it's credentials are the only ones who have access to the MCP server and should be the only ones who are able to call it.