anchor.diff:  my_segment     org1, org2
   </pre>
   
  -### <a id="list_is_org"></a> Display Isolation Segments Enabled for an Org
  +### <a name="list_is_org"></a> Display Isolation Segments Enabled for an Org
   
   An admin can entitle an org to multiple isolation segments.
   
  
positive.code: This topic describes how operators can isolate deployment 
  workloads into dedicated resource pools called isolation segments.
  
  ## <a id='overview'></a> Requirements
  
  You must have the [v.6.26.0](https://github.com/cloudfoundry/cli/releases/tag/v6.26.0) version or later of the [Cloud Foundry Command Line Interface (cf CLI)](../cf-cli/install-go-cli.html) installed to manage isolation segments.
  
  Target the API endpoint of your deployment with `cf api` and log in with `cf login` before performing the procedures in this topic. <%= vars.api_endpoint_book %>
  
  ## <a id='overview'></a> Overview
  
  <%= vars.isolation_segments_intro %>
  
  
negative.code: * [Reset the isolation segment assignment for a space](#reset_space)
  
  <% if vars.product_name == 'CF' %>
  ## <a name="bosh-segments"></a>Prepare BOSH to Support Isolation Segments
  
  To enable isolation segments for a deployment, you must first assign Diego cells a `placement_tags` property in your Diego manifest by following the steps below:
  
  