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 Submitted
Created by Guest
Created on Oct 9, 2026

RELATED IDEAS

MULTI-DOMAIN-LAYER — Digital multi-domain layering for cross-domain agent orchestration

watsonx Orchestrate should support explicit multi-domain layering: the ability to compose agents that operate in different domains (IT, HR, finance, supply chain, facilities) into stacked layers with defined handoffs, shared context, and domain-boundary permissions. Today's multi-agent setups are flat — every agent sees the same tools or builders hand-wire brittle integrations, which breaks least-privilege and makes cross-domain workflows unauditable. This proposal adds: (a) domain layers as first-class objects, each with its own tool allowlist, data residency, and approval policy; (b) typed handoff contracts between layers so an IT agent can pass a verified result to a finance agent without exposing raw credentials or PII; (c) a layer map view showing the full cross-domain flow for audit; (d) per-layer spend and risk budgets. Benefits: enterprises get genuinely cross-functional automation without flattening their security model, auditors get a legible map of who touched what across domains, and builders stop re-implementing plumbing for every cross-domain workflow.

Idea priority Low
  • Post comment

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.