---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure domain separation for Metric Intelligence

# Configure domain separation for Metric Intelligence {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure Metric Intelligence for domain separation to create logically defined domains that limit unauthorized access to data.

## Before you begin

Role required: evt_mgmt_admin and evt_mgmt_integration

## Procedure

1. Activate the Domain Support -- Domain Extension Installer plug-in.
2. Configure the MID Server for Operational Intelligence as a user that belongs to the desired domain with the role 'mid_server' assigned to it.
3. Configure a MID Server distributed cluster in the domain you desire and add Operational Intelligence MID Servers that belong to the same domain.  
   For more information about setting up MID Servers for Metric Intelligence , see [MID Server and MID Server distributed cluster for Metric Intelligence](https://servicenow-prod.fluidtopics.net/DcamS9mL07GSG9LDpkeOlQ "Using Metric Intelligence requires at least one MID Server distributed cluster which contains a single MID Server that is configured for Metric Intelligence.").  
   Note:  
   The Event Management's binding events are configured using the domain of the logged-in MID Server user. Once the process has finished, the record's domain is updated to use the domain from the CI so that any user within that domain can see the metric data.
{#configure-domain-separation-for-metric-intelligence__steps_bh3_tnv_ytb}