Orgs, Spaces, Roles, and Permissions
PWS uses a role-based access control (RBAC) system to grant Pivotal Web Services (PWS) users permissions appropriate to their role within an org or a space. This topic describes how orgs and spaces work within a PWS deployment, and how different Pivotal Web Services (PWS) User roles operate within those contexts.
Admins, Org Managers, and Space Managers can assign user roles using the cf CLI.
Note: Before you assign a space role to a user, you must assign an org role to the user.
Orgs
An org is a development account that an individual or multiple collaborators can own and use. All collaborators access an org with user accounts. Collaborators in an org share a resource quota plan, applications, services availability, and custom domains.
By default, an org has the status of active. An admin can set the status of an org to suspended for various reasons such as failure to provide payment or misuse. When an org is suspended, users cannot perform certain activities within the org, such as push apps, modify spaces, or bind services. For details on what activities are allowed for suspended orgs, see Roles and Permissions for Suspended Orgs.
User Accounts
A user account represents an individual person within the context of a PWS installation. A user can have different roles in different spaces within an org, governing what level and type of access they have within that space.
Before you assign a space role to a user, you must assign an org role to the user. The error message Server error, error code: 1002, message: cannot set space role because user is not part of the org
occurs when you try to set a space role before setting an org role for the user.
Spaces
Every application and service is scoped to a space. Each org contains at least one space. A space provides users with access to a shared location for application development, deployment, and maintenance. Each space role applies only to a particular space.
Roles and Permissions
A user can have one or more roles. The combination of these roles defines the user’s overall permissions in the org and within specific spaces in that org.
For non-admin users, the cloud_controller.read
scope is required to view resources, and the cloud_controller.write
scope is required to create, update, and delete resources.
Org Managers are managers or other users who need to administer the org.
Org Auditors view but cannot edit user information and org quota usage information.
- Org Billing Managers create and manage billing account and payment information.
Org Users can view the list of other org users and their roles. When an Org Manager gives a person an Org or Space role, that person automatically receives Org User status in that Org.
Space Managers are managers or other users who administer a space within an org.
Space Developers are application developers or other users who manage applications and services in a space.
Space Auditors view but cannot edit the space.
Roles and Permissions for Active Orgs
The following table describes the permissions for various PWS roles.
Activity | Org Manager | Org Auditor | Org Billing Manager | Space Manager | Space Developer | Space Auditor |
---|---|---|---|---|---|---|
Scope of operation | Org | Org | Org | Space | Space | Space |
Add and edit users and roles | ✓ | ✓ | ||||
View users and roles | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Create and assign org quota plans* | ||||||
View org quota plans | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Create orgs | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
View orgs | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Edit, rename, and delete orgs | ✓ | |||||
Create and assign space quota plans | ✓ | |||||
Create spaces | ✓ | |||||
View spaces | ✓ | ✓ | ||||
Edit spaces | ✓ | ✓ | ✓ | |||
Delete spaces | ✓ | |||||
Rename spaces | ✓ | ✓ | ||||
View the status, number of instances, service bindings, and resource use of applications | ✓ | ✓ | ✓ | ✓ | ||
Add private domains | ✓ | |||||
Deploy, run, and manage applications | ✓ | |||||
Instantiate and bind services to applications | ✓ | |||||
Associate routes, instance counts, memory allocation, and disk limit of applications | ✓ | |||||
Rename applications | ✓ | |||||
Set payment information and org/space spending limit | ✓ | |||||
Read invoices and payment history; set invoice notification email addresses | ✓ |
* Managed by PWS administrators.
Roles and Permissions for Suspended Orgs
The following table describes roles and permissions applied after an operator sets the status of an org to suspended.
Activity | Org Manager | Org Auditor | Org Billing Manager | Space Manager | Space Developer | Space Auditor |
---|---|---|---|---|---|---|
Scope of operation | Org | Org | Org | Space | Space | Space |
Add and edit users and roles | ||||||
View users and roles | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Create and assign org quota plans | ||||||
View org quota plans | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Create orgs | ||||||
View all orgs | ||||||
View orgs where user is a member | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Edit, rename, and delete orgs | ||||||
Create and assign space quota plans | ||||||
Create spaces | ||||||
View spaces | ✓ | ✓ | ||||
Edit spaces | ||||||
Delete spaces | ||||||
Rename spaces | ||||||
View the status, number of instances, service bindings, and resource use of applications | ✓ | ✓ | ✓ | ✓ | ||
Add private domains | ||||||
Deploy, run, and manage applications | ||||||
Instantiate and bind services to applications | ||||||
Associate routes, instance counts, memory allocation, and disk limit of applications | ||||||
Rename applications | ||||||
Set payment information and org/space spending limit | ||||||
Read invoices and payment history | ✓ |