anchor.diff:  my_segment     org1, org2
   </pre>
   
  -### <a id="list_orgs"></a> List Orgs for an Isolation Segment
  -
  -The following example request returns a list of orgs in the isolation segment with the given GUID. The request only returns orgs that you can access:
  -
  -<pre class="terminal">
  -$ cf curl "/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/organizations"
  -</pre>
  -
  -The request returns a list of orgs in the following format:
  -<pre class="terminal">
  -HTTP/1.1 200 OK<br>
  -{
  -  "data": [
  -    {
  -      "name": "my\_org",
  -      "guid": "45a66ed9-cb76-46c3-92dd-b29187b50bfb",
  -      "link": "/v2/organizations/45a66ed9-cb76-46c3-92dd-b29187b50bfb"
  -    },
  -    {
  -      "name": "my\_other\_org",
  -      "guid": "d0540a63-3bec-42ff-abd9-8a30328ba296",
  -      "link": "/v2/organizations/d0540a63-3bec-42ff-abd9-8a30328ba296"
  -    }
  -  ]
  -}
  -</pre>
  -
  -### <a id="list_spaces"></a> List Spaces for an Isolation Segment
  -
  -The following example request returns a list of spaces in the isolation segment with the given GUID. The request only returns spaces that you can access:
  -<pre class="terminal">
  -$ cf curl "/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913/relationships/spaces" 
  -</pre>
  -
  -The request returns a list of spaces in the following format:
  -<pre class="terminal">
  -HTTP/1.1 200 OK<br>
  -{
  -  "data": [
  -    {
  -      "name": "my\_space",
  -      "guid": "68d54d31-9b3a-463b-ba94-e8e4c32edbac",
  -      "link": "/v2/spaces/68d54d31-9b3a-463b-ba94-e8e4c32edbac"
  -    },
  -    {
  -      "name": "my\_other\_space",
  -      "guid": "b19f6525-cbd3-4155-b156-dc0c2a431b4c",
  -      "link": "/v2/spaces/b19f6525-cbd3-4155-b156-dc0c2a431b4c"
  -    }
  -  ]
  -}
  -</pre>
  -
  -## <a id="get_is"></a> Retrieve an Isolation Segment
  -
  -To retrieve an isolation segment by its GUID, send a `cf curl` command like the following to the `isolation_segments/GUID` endpoint of your CAPI:
  -<pre class="terminal">
  -$ cf curl "/v3/isolation_segments/323f211e-fea3-4161-9bd1-615392327913" 
  -</pre>
  -
  -This example request returns the [contents](#contents) of the isolation segment:
  -<pre class="terminal">
  -HTTP/1.1 200 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"
  -      }
  -   }
  -}
  +### <a id="list_is_org"></a> Display Isolation Segments Enabled for an Org
  +
  +An admin can enable multiple isolation segments for an org.
  +
  +To view the isolation segments that are enabled for an org, use the `cf org ORG-NAME` command. For example:
  +
  +<pre class="terminal">
  +$ cf org my-org
  +</pre>
  +
  +The command returns results similar to the following:
  +
  +<pre class="terminal">
  +Getting info for org my-org as user@example.com...
  +
  +name:                 my-org
  +domains:              example.com, apps.example.com
  +quota:                paid
  +spaces:               development, production, sample-apps, staging
  +isolation segments:   my_segment, my_other_segment
  +</pre>
  +
  +### <a id="list_is_space"></a> Show the Isolation Segment Assigned to a Space
  +
  +An admin can assign only one isolation segment to a space.
  +
  +To view the isolation segment assigned to a space, use the `cf space SPACE-NAME` command. For example:
  +
  +<pre class="terminal">
  +$ cf space staging
  +</pre>
  +
  +The command returns results similar to the following:
  +
  +<pre class="terminal">
  +name:                staging
  +org:                 my-org
  +apps:
  +services:
  +isolation segment:   my_segment
  +space quota:
  +security groups:     dns, p-mysql, p.mysql, pcf-redis, public_networks, rabbitmq, ssh-logging
   </pre>
   
   ## <a id="manage_is"></a> Manage an Isolation Segment
   
  -The `cf curl` requests and `cf CLI` commands listed in the sections below make changes to isolation segment objects in the CCDB. Only admins can make these changes.
  -
  -### <a id="update_is"></a> Update an Isolation Segment
  -
  -The following example renames the isolation segment with the given GUID to `my_isolation_segment`:
  -<pre class="terminal">
  -$ cf curl "/v3/isolation\_segments/323f211e-fea3-4161-9bd1-615392327913" \
  -  -X PATCH \
  -  -d '{
  -    "name": "my\_isolation\_segment"
  -  }'
  -</pre>
  -
  -The request returns the following output:
  -<pre class="terminal">
  -HTTP/1.1 200 OK<br>
  -{
  -   "guid": "323f211e-fea3-4161-9bd1-615392327913",
  -   "name": "my\_isolation\_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>
  +The `cf curl` requests and cf CLI commands listed in the sections below make changes to isolation segment objects in the CCDB. Only admins can make these changes.
   
   ### <a id="delete_is"></a> Delete an Isolation Segment
   
  +<p class="note"><strong>Note</strong>: An isolation segment with deployed apps cannot be deleted.</p>
  +
   The following command deletes an isolation segment:
   <pre class="terminal">
   $ cf delete-isolation-segment
  
positive.code: 
  The command fails if another isolation segment with the same name exists.
  
  ## <a id="lists"></a> List Isolation Segment Information
  
  The `cf isolation-segments` command retrieves information for the isolation segments that you have access to. The isolation segments you can see information for depends on your role, as follows:
  
  * **Admins** see all isolation segments in the system.
  * **Other users** see the isolation segments that their orgs have been added to.
  
negative.code: 
  <strong><%= modified_date %></strong>
  
  This topic describes how operators can isolate application 
  workloads to dedicated resource pools called isolation segments.
  
  ## <a id='overview'></a> Requirements
  