anchor.diff:    }'
   </pre>
   
  -
   ### <a id="add_remove_space_is"></a> Add or Remove Spaces in an Isolation Segment
  -
   
   Only admins and org managers can add or remove space in an isolation segment.
   
  
positive.code: 
  ### <a id="delete_is"></a> Delete an Isolation Segment
  
  The following example deletes an isolation segment with the given GUID:
  <pre class="terminal">
  $ cf curl "/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913" -X DELETE 
  </pre>
  
  The request outputs the following:
  <pre class="terminal">
  HTTP/1.1 204 No Content
  </pre>
  
  ## <a id="relationships"></a> Manage Isolation Segment Relationships
  
  The `cf 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 `cf 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">
  $ cf curl "/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/organizations" \
    -X POST \
    -d '{
      "data": [
        { "guid":"45a66ed9-cb76-46c3-92dd-b29187b50bfb" },
        { "guid":"d0540a63-3bec-42ff-abd9-8a30328ba296" }
      ]
    }' 
  </pre>
  
  The request outputs the following:
  <pre class="terminal">
  HTTP/1.1 201 OK<br>
  {
     "guid": "323f211e-fea3-4161-9bd1-615392327913",
     "name": "my\_segment",
     "created\_at": "2016-10-19T20:25:04Z",
     "updated\_at": "2016-11-08T16:41:26Z",
     "links": {
        "self": {
           "href": "https<span>:</span>//api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913"
        },
        "spaces": {
           "href": "https<span>:</span>//api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/spaces"
        },
        "organizations": {
           "href": "https<span>:</span>//api.example.org/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/organizations"
        }
     }
  }
  </pre>
  
  If an org is entitled to only one isolation segment, that isolation segment does not automatically become the default isolation segment for the org. You must explicitly [set the default isolation segment](#set_org_default_is) of an org.
  
  ### <a id="remove_org_is"></a> Remove Orgs from an Isolation Segment
  
  The following example removes two orgs from an isolation segment:
  <pre class="terminal">
  $ cf curl "/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/organizations" \
    -X DELETE \
    -d '{
      "data": [
        { "guid":"45a66ed9-cb76-46c3-92dd-b29187b50bfb" },
        { "guid":"d0540a63-3bec-42ff-abd9-8a30328ba296" }
      ]
    }'
  </pre>
  
  The request outputs the following:
  <pre class="terminal">
  HTTP/1.1 204 No Content
  </pre>
  
  <p class='note'><strong>Note</strong>: You cannot remove an org from an isolation segment if the isolation segment contains a space within that org or if it is the default isolation segment for that org.</p>
  
negative.code: <pre class="terminal">
  $ cf curl "/v2/spaces/68d54d31-9b3a-463b-ba94-e8e4c32edbac/isolation_segment" -X DELETE 
  </pre>
  
  ### <a id="assign_iso_seg"> Assign an Isolation Segment to a Space
  
  Admins can assign an isolation segment to a specific space. Apps in that space start in the specified isolation segment.
  
  To set a space's isolation segment, you must first entitle the space's org to the isolation segment.
  
  The following command assigns an isolation segment to a space:
  <pre class="terminal">
  $ cf set-space-isolation-segment SPACE\_NAME SEGMENT_NAME
  </pre>
  
  For example:
  <pre class="terminal">
  $ cf set-space-isolation-segment space1 my_segment
  </pre>
  