forked from jasonkeene/docs-rabbitmq-staging
-
Notifications
You must be signed in to change notification settings - Fork 0
/
control-access.html.md.erb
31 lines (21 loc) · 1.22 KB
/
control-access.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
---
breadcrumb: VMware RabbitMQ for Tanzu Application Service Documentation
title: Controlling Access to Service Plans by Org
owner: London Services
---
If you want to restrict access to a service plan to a specific org, follow the instructions below.
You can also limit the number of service instances by setting quotas---for instructions, see [Setting Limits for On-Demand Instances](./set-quotas.html).
## <a id="access"></a> Change Access to Service Plans
<p class="note"><strong>Note</strong>: If the plan you are restricting is currently enabled for all orgs,
you must first <strong>Disable Service Access</strong> for the plan, then grant access to the plan to specific orgs.
Use the <strong>CF Service Access</strong> field to deactivate access in the <a href="./install-config.html#service-plan"> service plan configuration.</a></p>
To restrict access to a plan for a specific org, run this command:
```
cf enable-service-access p.rabbitmq -p PLAN_NAME -o ORG_NAME
```
For example:
<pre class="terminal">
$ cf enable-service-access p.rabbitmq -p my-cluster-plan -o my-dev-org
</pre>
For more information about the above command,
see [Access Control](https://docs.pivotal.io/application-service/services/access-control.html).