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 Sep 1, 2025

PII detection for labeling or automated scrubbing

Identifying Personally Identifiable Information (PII) in field text is vital for compliance and security purposes to have some call out around PII, or automated scrubbing.

We have setup our own PII guardrail as an LLM call to pick up some specific fields, but it would be good if this was added into WXO itself.

At the moment we have something like this, which we have set up to extract fields we have coded in manually, then it removes them from the incident we submit to Open Pages, but i believe they would still be present in the logs.

Screenshot shows some high level categories; the ones we have setup already are:

  • Names

  • Phone numbers

  • Email address

  • Home addresses

  • Business addresses

  • Date of birth (but is hard as we have other dates we want to capture)

Idea priority Urgent
  • Guest
    Dec 3, 2025

    I will add a comment here as it aligns most with a question we received during a bootcamp from Liberty Mutual's HR team as part of a pre-sales engagement. They wanted to know if Orchestrate automatically scrubs out any PII or HAP data from its logs/agent responses. They were mostly interested in how Orchestrate handles sensitive HR queries and/or personal information a user might share. We saw that these filters are configurable in watsonx.ai as guardrail filters, but is still a work in progress for Orchestrate.

  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Oct 6, 2025

    We recently introduced events & instance methods support for embedded chat.

    This might enable the UI Builder persona to come in and handle PII for her instance of embedded chat & help while we look into what you are asking exactly.

  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Oct 2, 2025

    Regarding PII Detection (now focus of the present idea) this does not apply just to flows but any chat interactions I assume.

  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Oct 2, 2025

    Regarding requirements, we created a few from the original idea :

    Keeping the present record for PII Detection:

  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Oct 2, 2025

    Thank you very much for your input, we appreciate your work and support!

    I just want to make sure we act on all your point so let make sure that

    • all unexpected behavior(per doc) / likely defect gets reported to tech support to isolation / resolution (no need to report them here as well)

    • all improvements of existing features or as new feature are recorded in dedicated ideas so we can track / scope / prioritize those accordingly

    We hope this makes sense, so we can act on each item appropriately, thank you again!

1 MERGED

Configuration option to hide individual input and output fields displayed during tool execution

Merged
At present, all inputs and outputs from tool execution are displayed to the user without filtering. This can include sensitive information such as API keys or authentication credentials that should not be exposed. To address this, we request the f...
3 months ago in  1 Future consideration
1 MERGED

PII Redaction configuration

Merged
Enable configurable PII redaction where users can select which types of PII (e.g., emails, phone numbers, IDs) to detect and redact. Support masking styles, custom patterns, role-based visibility, and audit logs for compliance.
6 months ago in  0 Future consideration