Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

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 Under review
Created by Guest
Created on Aug 6, 2025

SNOW connector should support domains (within a ServiceNow instance)

Domain separation allows for the logical isolation of different areas within a single ServiceNow instance. Hence, domains separate data, configurations, and processes within the same SNOW instance. This separation of data is key when multiple entities need to share a single ServiceNow instance. 

The more we talk to customers, the more cases we find where domains are currently used in SNOW. One of these customers is TELUS. TELUS needs to route incident records through the SNOW connector to a specific domain within their SNOW instance. And this routing should be based on the properties of the incident record. In other words, the values of properties/fields in the incident should be used as the determining factor: which domain to send the incident record to.

The current implementation of the SNOW OOTB connector does not take domains into account (instead, it works with the "global" domain). Therefore, this idea can be summed up as: 

- Add support for domains within a SNOW instance.

- Add capability to specify domain routing rules based on the values of the fields in the incident record (maybe through an Automation policy).

Idea priority High