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 Dec 4, 2025

Define tool parameters as sensitive for redaction

There is no support for masking PII in trace logs today, exposing potentially sensitive information and introducing security risks for customers. The solution delivered as part of https://watson-orchestrate.ideas.ibm.com/ideas/LSABER-I-1444 only masks specific patterns, so it’s hard to say we cover all possible sensitive formats (e.g., for example, we don’t have a comprehensive list of national identifiers similar to SSNs from other countries). As customers start to deploy context variables, they will ask for redaction of content stored in context variables.

  • As a builder, I can add metadata to the tool definition that clearly labels specific parameters (like password, OTP, or the last four digits of a credit card) as sensitive.

  • Any parameter marked as sensitive is redacted from traces and the logs UI

  • Ability to redact content stored and passed via context variables (e.g. in trace logs)