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 Submitted
Created by Guest
Created on Nov 18, 2025

Ability to disable tools and agents in the catalog

The EY security team has a requirement to make all tools and agents that are in the catalog to be reviewed and approved first before they become available to their end users including the Builders.

As Administrators of a watsonx orchestrate instance, they should have the ability to disable and enable any tools and agents in their catalog. When disabled, a tool or agent is either (a) completely hidden and unknown from all users  OR (b) shown but users should not be able to click on it nor be able to use or call it. At the moment, 90% of these tools and agents are not approved and therefore, they'd prefer that their initial state is disabled. The ability to enable/disable them should be available in the UI or via the ADK but only the administrators should be able to do this action.

Idea priority Urgent