anchor.diff:  
   ### <a id="set_org_default_is"></a> Set a Default Isolation Segment for an Org
   
  -If an org has resources in multiple isolation segments, one segment serves as the default, and new spaces created within the org will be in its default isolation segment unless specified otherwise.
  +Only admins and org managers can set the default isolation segment of an org.
  +
  +When an org has a default isolation segment, new spaces created within the org will be in this default isolation segment unless specified otherwise.
   
   You set the default isolation segment for an org by sending a request to the endpoint for the organization, setting its `default_isolation_segment_guid` data property to the GUID of the new default isolation segment. For example:
   
  
positive.code: The `curl` requests listed in the sections below retrieve information for the isolation segments that you have access to, filtered by [parameters](http://v3-apidocs.cloudfoundry.org/version/3.0.0/index.html#list-isolation-segments) that you can include. The isolation segments you can see information for depends on your role, as follows:
  
  * **Admins** see all isolation segments in the system.
  * **Org Managers** see isolation segments containing orgs that they belong to.
  * **Other users** see isolation segments containing spaces that they belong to.
  
  ### <a id="list_is"></a> List Isolation Segments
  
  
negative.code: 
  ## <a id="relationships"></a> Manage Isolation Segment Relationships
  
  The `curl` requests listed in the sections below add and remove orgs and spaces from isolation segments. 
  
  ### <a id="add_org_is"></a> Add Orgs to an Isolation Segment
  
  Only admins can add orgs to isolation segments.
  
  In the data field of the `curl` command, specify one or more orgs by GUID to add to the isolation segment. The following example adds two orgs to an isolation segment:
  <pre class="terminal">
  