Domain Separation and NOW ASSIST

[martinSchwaigho]

Hey there, 

I’m currently working with a domain-separated ServiceNow environment and exploring the integration of Now Assist functionalities. While I’m aware that certain components of Now Assist, support domain separation (

https://www.servicenow.com/docs/bundle/xanadu-it-service-management/page/product/change-management/c...), I’m seeking clarity on whether all Now Assist features enforce domain separation.

• Specifically, my concerns revolve around Data Isolation: Ensuring that prompts or actions initiated in Domain A do not access or retrieve data from Domain B.
  • Example: The NOW Assist skill for Change Request Risk Analysis, can include the history of changes on the instance as a further metric for expected risk. Here I would like to avoid the inclusion of Changes that are outside of the users domain. 
• Additionally I am curious about AI Search: Clarifying the domain separation capabilities of Now Assist in AI Search, as documentation on this seems limited.

I understand that GlideRecord operations respect domain separation through before-query business rules (https://www.servicenow.com/docs/bundle/yokohama-platform-security/page/administer/company-and-domain...). However, given that Now Assist operates as a more abstracted layer, I am not sure if that also applies to those use cases.

Are there best practices, configurations, or documentation that detail how Now Assist maintains domain separation across its various components?

Any insights or experiences shared would be greatly appreciated.

Cheers,

Martin 

[PaulSylo]

Hi @martinSchwaigho 

Great Question Martin ! i would try to answer based on my understanding , since Now assist runs on top of the platform, Data queries generally follow domain separations( Iike ACLS and before query rules). May be some skills like ( as you mentioned) Change risk analysis may need extra filtering to avid pulling data across domains. you may need to add restriction in your custom skills. 

For AI search , Domain separation is unsupported for the AI Search application tables, but user search queries respect domain restrictions from indexed Now Platform table records.

refer this interesting pointers- https://www.servicenow.com/docs/bundle/yokohama-platform-administration/page/administer/ai-search/co...

https://www.servicenow.com/docs/bundle/yokohama-platform-administration/page/administer/ai-search/co...