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.
Thank you for this idea and for the detailed business impact context.
We have a clarifying question to make sure we are solving the right problem for you:
Option A — Domain-based catalog sections: The catalog home page gains dedicated sections per domain (Finance, HR, IT, etc.), making it easy to browse agents grouped by category. Would this meet the customer's need for navigating hundreds of agents by group?
Option B — Role-based default catalog views: Are you specifically looking for personalised views where different users within your tenant automatically see a filtered catalog based on their job role — e.g. Finance users see only Finance agents by default? This would be a separate capability requiring admin-configured role profiles.
Your answer will help us determine whether we fully addresses this idea, or whether we need a separate role-defaulted view epic. Any additional context on how users currently navigate the catalog today would also be very helpful.