Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Domain separation in Service Level Management

Log in to subscribe to topics and get notified when content changes.

Domain separation in Service Level Management

This is an overview of domain separation and Service Level Management. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

Overview

Support: Level 2

Domain separation is supported in this application. Not all ServiceNow applications support domain separation; some include limitations on the data and administrative settings that can be domain separated. To learn more, see Application support for domain separation.

  • Service Level Management helps customers monitor, measure, and report on agreed service level agreements (SLAs); SLA definitions encapsulate these agreements.
  • Users can see only content in the domain to which they have access.

How domain separation works in Service Level Management

The intention of SLM is to provide customers with an expectation of service within a known timescale and the ability to monitor when service levels are not being met. To learn specific terms and definitions see Service Level Management concepts .

  • SLA definitions and task SLAs have domain fields. However, task SLAs are created only in the domain of its attached task record.
  • SLA definitions must be defined in a tenant domain (or global) in order for task SLAs to be created and attached to a given task (or extensions).
  • Task SLAs attach to a task if an SLA definition exists in the task records domain or in an ancestor domain.
  • Task SLAs always inherit the domain of its attached task record, which includes the workflow running on the task SLA record.
    • If a task record ever flips, the task SLA also flips.
  • If an SLA definition exists in an ancestor’s domain, the definition can be overridden in a sub-domain (delegated administration).

Domain separated tables

  • SLA definition [contract_sla]
  • Task SLA [task_sla]

Use cases

  • An ESS user in the ACME domain logs in and creates an incident, at which point an SLA is attached. The SLA is created in the domain of the associated task record (incident), which is the ACME domain. The ESS user is not able to read SLA records. These are restricted to the following roles:
    • Administrator
    • ITIL
    • SLA Administrator
    • SLA Manager
  • An ITIL user in the Acme domain logs in and creates an incident. The process above is the same except that the ITIL user can read the SLA record attached to the incident.
  • If an SLA definition exists in the Acme domain and doesn’t meet the needs of an Acme sub-domain (Acme child) an SLA Administrator can remediate. SLA Administrators can navigate to the ACME SLA definition when their session domain is ACME child, make the relevant changes, and save them. The SLA Administrator is alerted that an override has been created.
  • An ITIL user sets the session domain to Acme child and creates an incident. The task SLA is created using the SLA definition from Acme child.
Feedback