Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Domain separation and Enterprise Asset Management

Domain separation is supported in Enterprise Asset 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.

Overview

Domain separation support in the product enables service providers to offer managed services for enterprise asset management to their customers. This feature also caters to large organizations who manage their subsidiaries as independent domains.

How domain separation works in Enterprise Asset Management

In Enterprise Asset Management, domain separation occurs in two stages: data separation and process separation. There are two system properties that are used to enable or disable the separation. In the Tokyo release, both data and process are domain-separated.

Note:

The Recommended practice is to avoid customizing the base system domain configuration record.

Required plugins

  • Domain separation extension (com.glide.domain.msp_extensions.installer)
  • Performance Analytics – Domain Support (com.snc.pa.domain_support)
  • Work management (com.snc.work_management)

Other supported plugins

  • Service Catalog – Domain Separation (com.glideapp.servicecatalog.domain_separation)
  • Procurement (com.snc.procurement)

To learn more, see Domain separation explained, Contains queries and domain access, and Importance of Default domain.

Parent Topic:Enterprise Asset Management reference

Related topics

Components installed with Enterprise Asset Management

OT Asset Workspace roles

Asset fields for enterprise assets

Asset audit fields for enterprise assets

Audit results

Enterprise model categories and corresponding classes

Mandatory fields in the bulk import spreadsheets

Normalization status for enterprise models

Model fields for Enterprise Asset Management

Contract fields for Enterprise Asset Management

Maintenance plan fields for Enterprise Asset Management

Maintenance schedule fields for Enterprise Asset Management

Work plan fields for Enterprise Asset Management

Work plan schedule fields for Enterprise Asset Management

Expense line fields for Enterprise Asset Management

Fields inherited from a parent asset group to a sub group

Enterprise asset disposal order stages

Terminology for linear assets

Scheduled jobs and tables installed with normalization of firmware models

Asset put away task fields

Domain separation for service providers