---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Domain separation and Automated Test Framework

# Domain separation and Automated Test Framework {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Domain separation is supported in the Automated Test Framework. 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: Standard\* {#domain-separation-auto-test-framework__section_chp_ncm_ylb}

The
support level is Standard but has some exceptions or special conditions.{#domain-separation-auto-test-framework__p_usc_nfg_h1c}

* Includes all aspects of Basic level support.
* Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
* The instance owner must be able to configure minimum viable product (MVP) business logic and data parameters. This configuration is done per tenant, as expected for the specific application.

{#domain-separation-auto-test-framework__ul_fgh_3dx_zkb}

Sample use case: An admin must be able to make comments required when a record closes for
one tenant, but not for another.{#domain-separation-auto-test-framework__p_vsc_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-auto-test-framework__p_wsc_nfg_h1c}

## ATF use case {#domain-separation-auto-test-framework__section_hhf_3sh_wkb}

Automated test framework design and runtime access are solely for the owner of the instance to
validate domain-specific processes. By designing tests for my customers we confirm results per
tenant.

## Testing {#domain-separation-auto-test-framework__section_rhx_12n_trb}

When testing domain separation during ATF test steps, you must set the domain first. This
should be part of the first impersonation step of each of the ATF test steps when they are
dependent on a domain being set. To learn more about domain separation recommended practices,
see [Domain separation recommended practices for
service providers](https://www.servicenow.com/docs/access?context=bp-domain-sep-recommended&version=australia&pubname=australia-platform-security&ft:locale=en-US)
**Tópicos relacionados**   

* [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)