anchor.diff:  ---
   
   
  -<p class="note warning"><strong>WARNING</strong>: Service instance sharing is a beta feature and may be removed at any time without notice. Use at your own risk.</p>
  +<p class="note warning"><strong>WARNING</strong>: Service instance sharing is a beta feature and may be removed at any time without notice.
  +Use at your own risk.</p>
   
   Sharing a service instance between spaces allows apps in different 
  -spaces to share databases, messaging queues and many other types of services. 
  +spaces to share databases, messaging queues, and other types of services.
   This eliminates the need for development teams to use service keys and 
   user-provided services to bind their apps to the same service instance that was 
  -provisioned using the `cf create-service` command. Sharing service instances 
  -improves security, auditing, and provides a more intuitive user experience.
  +provisioned using the `cf create-service` command.
  +Sharing service instances improves security, auditing, and provides a more intuitive user experience.
   
  -For example, if two development teams have applications in their own spaces, 
  -and both of those applications want to send messages to each other using a 
  -messaging queue, the development team in space A could create a new instance of 
  -a messaging queue service, bind it to their application, and share that service 
  -instance into space B. 
  -A developer in space B could then bind their application to the same service 
  -instance, and the two applications could begin publishing and receiving 
  -messages from one another. 
  +For example, if two development teams have apps in their own spaces,
  +and both of those apps want to send messages to each other using a
  +messaging queue, you can do the following:
   
  -* Service instances can be shared into multiple spaces, across orgs.
  +1. The development team in space A can create a new instance of
  +a messaging queue service, bind it to their app, and share that service instance into space B.
  +
  +1. A developer in space B can then bind their app to the same service
  +instance, and the two apps can begin publishing and receiving
  +messages from one another.
  +
  +## <a id="about"></a> About Service Instance Sharing
  +
  +* Service instances can be shared into multiple spaces and across orgs.
   
   * Developers and administrators can share service instances between spaces
  -in which they have the SpaceDeveloper role. 
  +in which they have the Space Developer role.
   
   * Developers who have a service instance shared with them can only bind and 
  -unbind to that service instance. They cannot update, rename, or delete it.
  +unbind apps to that service instance. They cannot update, rename, or delete it.
   
  -* Developers who have a service instance shared with them will be able to see 
  +* Developers who have a service instance shared with them are able to see
   the values of any configuration parameters that were used to configure the 
   service instance when it was provisioned or updated.
   
   ## <a id="enabling"></a> Enabling Service Instance Sharing in Cloud Foundry
   
  -To enable service instance sharing, an administrator must enable the `service_instance_sharing` flag.
  +To enable service instance sharing, you must enable the `service_instance_sharing` flag.
   
   <pre class="terminal">
   $ cf enable-feature-flag service_instance_sharing
  
positive.code: $ cf unshare-service SERVICE-INSTANCE -s OTHER-SPACE [-o OTHER-ORG] [-f]
  </pre> 
  
  The optional `-f` flag forces an unshare without confirmation.
  
  ## <a id="security"></a> Security Considerations
  
  * [Service keys](./service-keys.html) cannot be created from a space that a 
  service instance has been shared into.  
  This ensures that developers in the space where a service instance has been 
  shared from have visibility into where, and how many times, the service 
  instance is used.
  
  * Sharing service instances does not automatically update application security 
  groups (ASGs). The network policies defined in the ASGs may need to be updated to ensure that applications using shared service instances can access the underlying service.
  
  * Access to a service must be enabled using the `cf enable-service-access` command for a service instance to be shared into a space.
  
  * Not all services are enable for sharing instances functionality. Contact the 
  service vendor directly if you are unable to share instances of their service. 
  If you are a service author, see [Enabling Service Instance Sharing](../../services/enable-sharing.html).
  
  ## <a id="disabling"></a> Disabling Service Instance Sharing in Cloud Foundry
  
  To disable service instance sharing, an administrator runs the following:
  
  <pre class="terminal">
  $ cf disable-feature-flag service_instance_sharing
  
negative.code: </pre>
  
  * You cannot share a service instance into a space where a service 
  instance with the same name already exists.
  
  * To share a service instance into a space, the space must have access to the 
  service and service plan of the service instance that you are sharing. Run the `cf enable-service-access` command to set this access.
  
  * If you no longer have access to the service or service plan used to create your service instance,
  you cannot share that service instance.
  
  ## <a id="unsharing"></a> Unsharing a Service Instance
  
  <p class="note warning"><strong>WARNING</strong>: Unsharing a service instance 
  automatically deletes all bindings to apps in the spaces it was shared into.
  This may cause apps to fail. Before unsharing a service instance,
  run the <code>cf service SERVICE-INSTANCE</code> command to see how many bindings exist in the spaces the service instance is shared into.</p>
  
  You can unshare a service instance if you have the Space Developer role in the
  space where this service instance was shared from.
  
  You cannot delete or rename a service instance until it is unshared from all 
  spaces.
  