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.

Add idea Subscribe
Status Future consideration
Created by Guest
Created on May 6, 2026

RELATED IDEAS

Enable administrators to strictly control and allowlist which knowledge sources (e.g., vector stores, file uploads, web search, third-party connectors) agents can use for grounding.

Enterprises require the ability to tightly govern what data sources agents can access for grounding responses to ensure compliance, security, and data residency requirements.

Currently, Watsonx Orchestrate allows agents to connect to various knowledge sources, including external or unapproved third-party systems, which may violate enterprise data boundary policies.

This feature would allow administrators to define and enforce policies that restrict knowledge sources to approved services only, such as internal vector stores, sanctioned document repositories, or enterprise-approved APIs.

It should include granular controls at the tenant, project, and agent level, along with auditing capabilities to track which sources are being used. This would ensure that agents only operate within approved enterprise data ecosystems.

Idea priority Urgent
  • Post comment
  • Admin
    Laurent Tillette de Clermont-Tonnerre
    May 14, 2026

    This could be partially addressed by this other requirement: https://watson-orchestrate.ideas.ibm.com/ideas/LSABER-I-1848

    Reply

By clicking the "Post Comment" or "Add Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not include IBM confidential, company confidential, or personal information in any field.
Having problems accessing this portal? Describe the problems in an email to ideasibm@us.ibm.com.