--- sourceDocument: Australia Financial Services Operations sourceDocumentLink: https://www.servicenow.com/docs/r/australia/financial-services-operations Release : - australia ft:locale : - en-US ft:publication_title : - Australia Financial Services Operations ft:clusterId : - finso bundleId : - finso workflow : - Customer and Industry --- # Domain separation and Individual Life Claims # Domain separation and Individual Life Claims {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Individual Life Claims Domain separation for the Individual Life Claims application allows the organization of data, processes, and administrative tasks into distinct domains. This feature enhances control over user access and visibility of data, supporting various service provider use cases. It is essential for maintaining the integrity of tenant-specific operations. Show full answer Show less ## Key Features * **Data Management:** Ensures accurate data allocation into the correct domain for service provider use. * **Runtime Support:** Domain separation is applied during runtime, affecting the user interface, cache keys, reporting, rollups, and aggregations. * **Domain-Separated Tables:** Key tables such as Consumer, Account, and Contact are domain-separated, along with newly created tables for claims management. ## Key Outcomes By implementing domain separation, users can effectively manage claims through structured workflows. For instance: * **Case Intake:** Agents can gather and manage claim information efficiently on behalf of customers. * **Claims Analysis:** Specialists can review claims comprehensively, request additional documentation, and make informed decisions regarding approvals or denials. This structured approach enhances the service delivery for both customers and service providers within the Individual Life Claims application. For more information on support levels, refer to the details on application support for domain separation. Domain separation is supported for the Individual Life Claims application. 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 {#domain-separation-individual-life-claims__section_or4_rmm_wbc} {#domain-separation-individual-life-claims__domain-sep-supported} * 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. {#domain-separation-individual-life-claims__ul_yhr_g2j_xkb} 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.{#domain-separation-individual-life-claims__p_lsc_nfg_h1c} For more information on support levels, see [Application support for domain separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=australia&pubname=australia-platform-security&ft:locale=en-US).{#domain-separation-individual-life-claims__p_msc_nfg_h1c} ## How domain separation works in Individual Life Claims {#domain-separation-individual-life-claims__section_pbs_rmm_wbc} All [FSO integrations](https://www.servicenow.com/docs/EhO58T0tEmDwyWmXVykt~w "The ServiceNow Financial Services Operations (FSO) solution helps financial services institutions to reduce costs through automation, improve customer satisfaction, and embed risk and compliance controls across workflows.") applications are built on top of and use many Customer Service Management (CSM) tables. The key reference tables are the customer tables such as Consumer, Account, and Contact, and these tables are domain-separated. ## Tables {#domain-separation-individual-life-claims__section_t3r_qxm_zbc} All new tables in Individual Life Claims are domain-separated: * sn_ins_claim_indl_death_case * sn_ins_claim_indl_death_task * sn_ins_claim_indl_rel_death_case {#domain-separation-individual-life-claims__ul_jph_sxm_zbc} ## Use cases {#domain-separation-individual-life-claims__section_qbs_rmm_wbc} Case Intake : The First-notice-of-loss (FNOL) intake agents can intake information for a life insurance claim (or similar product) on behalf of a customer. When the customer calls to file a claim, the intake agent gathers important information that is related to the claim, such as a description of the loss of life incident and any supporting documentation. After collecting the initial details, they open a claim case for a claims specialist to work on. Claims Analysis : A claims specialist works on a claim that they receive through the workspace dashboard. The specialist reviews the policy details. If necessary, they can request and review the additional information or documentation from the beneficiaries. The specialist sets the reserve funds, modifies the coverage exposures and reserve funds over time, and can also view all activity that is associated with handling the claim. The specialist can also make claim approval or denial decisions based on the available evidence. Note: Sometimes a ServiceNow® platform feature or application may be able to effectively support service provider use cases even though the domain framework is not being used. In this case, the application may be assigned Basic\*, Standard\*, or Enhanced\* for its domain support level, and include detailed use cases. For example: Before the New York release, Service Catalog had no domain support. But the instance owner was able to configure separate catalogs and items for each customer in a domain-separated instance. This allowed Service Catalog to be used at a Standard support level. To learn more, see domain separation [Application levels of support](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=australia&pubname=australia-platform-security&ft:locale=en-US). **Related topics** * [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=australia&pubname=australia-platform-security&ft:locale=en-US)