Domain separation and Asset Audit Response

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Domain separation and Asset Audit Response

    Asset Audit Response supports domain separation, enabling ServiceNow customers to logically segment data, processes, and administrative tasks into distinct domains. This separation controls user access and visibility, ensuring data integrity and confidentiality across multiple tenants. Domain separation is fully integrated across all Asset Audit Response features and tables without requiring additional configuration.

    Show full answer Show less

    Key Features

    • Basic support level: The application ensures data is assigned to the correct domain for service provider scenarios.
    • Run-time domain separation: Includes separation in the user interface, cache keys, reporting, rollups, and aggregations.
    • Automatic domain assignment: Evidence requests created in the Audit Workspace are automatically linked to corresponding asset evidence tasks in the Asset Governance Workspace under the same domain.
    • Multi-tenant readiness: Instance owners can configure the application to operate across multiple tenants effectively.

    Key Outcomes

    With domain separation in Asset Audit Response, service providers can manage audit engagements and evidence requests securely and efficiently within their respective domains. This ensures that tenant customers only see responses and data relevant to their domain, maintaining data segregation and compliance. Users can confidently leverage Audit Workspace, Asset Governance Workspace, and Software or Hardware Asset Management applications using consistent domain-specific data.

    Domain separation is supported for Asset Audit Response. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

    Support level: Basic

    • Business logic: Ensure that data goes into the proper domain for the application’s service provider use cases.
    • The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
    • The owner of the instance must set up the application to function across multiple tenants.

    Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer’s message, the customer must be able to see the SP's response.

    For more information on support levels, see Application support for domain separation.

    Overview

    Asset Audit Response supports domain-based data separation. This domain separation is available across all Asset Audit Response features and tables.

    How domain separation works in Asset Audit Response

    Domain separation in Asset Audit Response does not require any additional setup or configuration.

    When managing and completing an audit engagement and corresponding evidence request, ensure that you are using data from the same domain across the Audit Workspace, the Asset Governance Workspace, and either the Software Asset Management or Hardware Asset Management application.
    Note:
    If you create an evidence request under a specific domain in the Audit Workspace, the corresponding asset evidence task automatically falls under the same domain in the Asset Governance Workspace.