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:
stick to one feature enhancement per idea
add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)
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.
One of my partners is also asking for the same solution.
In the same tenant, they want some embedded agents to be secured while others can have embedded security disabled.
In the current Watson Orchestrate architecture, enabling security for the embedded chat applies at the tenant level, not at the individual agent level. This creates challenges because all users with embedded chat must use the same JWT token associated with the initial user who enabled security.
By shifting security enforcement to the agent level, only the specific agent would be affected, ensuring that other users within the tenant remain unaffected. This approach provides better isolation, flexibility, and reduces dependency issues across multiple users.
Thank you for your insight, are you referring to limiting access to agent based on user identify or else?