Domain separation and Incident Management

---
title: Domain separation and Incident Management
description: Domain separation is supported in Incident 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.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/it-service-management/incident-management/domain-separation-incident-management.html
release: brazil
product: Incident Management
classification: incident-management
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 2
breadcrumb: [Reference, Incident Management, IT Service Management]
---

# Domain separation and Incident Management

Domain separation is supported in Incident 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: Standard

-   Includes all aspects of **Basic** level support.
-   Application properties are domain-aware as needed.
-   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 configure the minimum viable product \(MVP\) business logic and data parameters per tenant as expected for the specific application.

Sample use case: An admin must be able to make comments required when a record closes for one tenant, but not for another.

For more information on support levels, see [Application support for domain separation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/domain-separated-apps.md).

## Incident Management purpose

-   The goal of Incident Management is to restore normal service operation as quickly as possible, while minimizing impact to business operations and maintaining quality.
-   Typically, end users log incidents when a service they are using is impacted or not available. Users with the itil role in your organization classify these incidents, route them as appropriate, and work to resolve them.
-   The incident and incident task tables support domain separation. So, the fulfillers see only incidents or incident tasks that have been created within the \(tenant\) domain that they belong to.

## Domain separation behavior in Incident Management

Fulfillers see only incidents and incident tasks that have been created within the \(tenant\) domain that they belong to.

## Incident Management domain separated tables

-   Incident \[incident\]
-   Incident Task \[incident\_task\]

## Incident Management use cases

-   An employee self-service \(ESS\) user in the Initech domain creates an incident. Only ITIL users in the Initech domain or the global domain can see this incident.
-   An ITIL user belonging to a parent domain can see incidents of all its child domains as well.
-   An ITIL user belonging to a specific domain can create incidents only on behalf of the domains that they have access to.
-   An ITIL user can associate child incidents only of those domains that they have access to.
-   If a user has access to multiple domains, the domain specified on the current record drives the functionality of that record and reference fields.

**Parent Topic:**[Incident Management reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/incident-management/reference-section-for-incident-management.md)

**Related topics**  


[Domain separation for service providers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/domain-sep-landing-page.md)