--- sourceDocument: Brazil Customer Success Management sourceDocumentLink: https://www.servicenow.com/docs/r/acct-lifecycle-events Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Customer Success Management ft:clusterId : - actle bundleId : - actle workflow : - Customer and Industry --- # Domain separation # Domain separation and Customer Success Management {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Customer Success Management The Customer Success Management (CSM) application supports domain separation, which allows you to logically separate data, processes, and administrative tasks into distinct domains. This separation controls access and visibility of data by user, ensuring that information is properly segmented across multiple tenants or accounts. Domain separation is essential for service providers managing interactions with different customers securely and efficiently. Show full answer Show less CSM enables creation and tracking of onboarding cases, tasks, objectives, outcomes, and documented plans to drive customer success. Key entities such as account onboarding cases, engagements, success objectives, risk signals, and internal plays are all domain separated at the account level, reinforcing data isolation per tenant. ## Key Features * **Runtime domain separation:** The application enforces domain separation dynamically, including user interface elements, cache keys, reporting, rollups, and aggregations. * **Account-level domain separation:** Onboarding cases and related tasks, as well as customer success activities like engagements and risk signals, are isolated by account domain. * **Domain separated data tables:** Multiple core CSM tables (e.g., onboarding cases, tasks, success objectives, plays, risk signals, and engagement health definitions) are configured to support domain separation. * **Support for multi-tenant environments:** Enables service providers to securely manage customer data and interactions across separate domains. * **Domain separation setup:** Requires enabling the domain separation plugin and the `csmautoaccountdomaingeneration` property for automatic domain assignment. ## Practical Benefits for ServiceNow Customers * Securely segment customer success data and processes per account or tenant, reducing risk of data leakage. * Support multi-tenant service provider use cases by ensuring tenant-specific data visibility and access. * Maintain clean reporting and analytics per domain to accurately reflect performance and health metrics for each customer. * Leverage domain separation to streamline administration and governance across diverse customer portfolios within one ServiceNow instance. Domain separation is supported for Customer Success Management. 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 {#account-lifecycle-domain-separation__section_pj5_slf_1cc} {#account-lifecycle-domain-separation__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. {#account-lifecycle-domain-separation__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.{#account-lifecycle-domain-separation__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=brazil&pubname=brazil-platform-security&ft:locale=en-US).{#account-lifecycle-domain-separation__p_msc_nfg_h1c} ## Overview of Customer Success Management {#account-lifecycle-domain-separation__section_ptt_xlf_1cc} With the Customer Success Management application, you can create onboarding cases and related onboarding case tasks, track objectives, outcomes, and define documented plans to ensure success. The account onboarding case and related tasks support domain separation at the account level. Engagements, objectives, outcomes, initiatives, success cases, risk signals and internal plays are domain separated at the account level. ## How domain separation works in Customer Success Management {#account-lifecycle-domain-separation__section_qtt_xlf_1cc} * Account onboarding cases, onboarding tasks, and data import case tasks are domain separated using the account domain. * All other staging tables used for the Data Import are not domain separated. * All customer success tables are domain separated. {#account-lifecycle-domain-separation__ul_ij3_f4h_dcc} ## Setting up domain separation in Customer Success Management {#account-lifecycle-domain-separation__section_wkg_l4h_dcc} Domain separation for Customer Success Management requires the domain separation plugin and enabling the csm_auto_account_domain_generation domain separation property. For more information on setting up domain separation, see [Domain separation and Customer Service Management](https://www.servicenow.com/docs/access?context=domain-separation-customer-service&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US). ## Domain separated tables {#account-lifecycle-domain-separation__section_ltk_54h_dcc} * Account onboarding case \[sn_acct_lc_onb_case\] * Data import task \[sn_ti_core_imp_task\] * Onboarding task \[sn_ti_core_task\] * Engagement \[sn_acct_lc_engagement\] * Success objective \[sn_acct_lc_success_objective\] * Success outcome \[sn_acct_lc_success_outcome\] * Success initiative \[sn_acct_lc_success_initiative\] * Customer play \[sn_acct_lc_success_case\] * Success task \[sn_acct_lc_success_task\] * Touchpoint \[sn_acct_lc_touchpoint\] * Internal play \[sn_acct_lc_internal_play\] * Internal play task \[sn_acct_lc_internal_play_task * Risk Signal and Issue (sn_acct_lc_risk_signal_issue) * Implementation Record (sn_acct_lc_implementation_record) * Risk Solution (sn_acct_lc_risk_signal_solution_relationship) * Engagement Health Definition (sn_acct_lc_eng_hlt_def) * Health Metric Configuration (sn_acct_lc_eng_hlt_mtr_config) * Engagement Risk Definition (sn_acct_lc_eng_risk_def) * Risk Threshold Override (sn_acct_lc_risk_threshold_override) * Risk Occurrence (sn_acct_lc_risk_occurrence) * Data Source (sn_data_ctx_engine_src) * Context Engine Mapper (sn_data_ctx_engine_map) * Context (sn_data_ctx_engine_ctx) * Context Engine Data (sn_data_ctx_engine_data) * Segment (sn_data_ctx_engine_brkdwn_seg) * Segment Configuration (sn_data_ctx_engine_seg_conf) * DCE Insight (sn_data_ctx_engine_insight) * DCE Insight Item (sn_data_ctx_engine_insight_item) * DCE Visualization (sn_data_ctx_engine_visualization) * DCE Visualization M2M (sn_data_ctx_engine_visualization_m2m) * Product Capability (sn_prod_cap_core_prod_cap) * Product Capability Map (sn_prod_cap_core_prod_cap_map) * Capability Relationship Map (sn_prod_cap_core_cap_rel_map) * Product Usage (sn_prod_cap_core_prod_usage) * Product Capability Usage (sn_prod_cap_core_prod_cap_usage) {#account-lifecycle-domain-separation__ul_n4f_v4h_dcc} **Related topics** * [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=brazil&pubname=brazil-platform-security&ft:locale=en-US)