LATEST VERSION: 1.9 - CHANGELOG
Pivotal Cloud Foundry v1.9

Orgs, Spaces, Roles, and Permissions

Page last updated:

PCF uses a role-based access control (RBAC) system to grant Elastic Runtime users permissions appropriate to their role within an org or a space. This topic describes how orgs and spaces work within a PCF deployment, and how different Elastic Runtime User roles operate within those contexts.

Admins, Org Managers, and Space Managers can assign user roles using the cf CLI  or Apps Manager.

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 PCF 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.

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.

  • Admin is a user role that has been assigned the cloud_controller.admin scope in UAA. An admin user has permissions on all orgs and spaces and can perform operational actions using the Cloud Controller API. To create an account with cloud_controller.admin scope for your installation, see Create an Admin User.
  • Admin Read-Only is a user role that has been assigned the cloud_controller.admin_read_only scope in UAA. This role has read-only access to all Cloud Controller API 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.

  • 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 PCF roles.

Activity Admin Admin Read-Only Org Manager Org Auditor Space Manager Space Developer Space Auditor
Scope of operation Org 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
Suspend or activate an org
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
Create and manage Application Security Groups

**Not by default, unless feature flag set_roles_by_username is set to true.

*Not by default, unless feature flag user_org_creation is set to true.

Unless disabled by feature flags.

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 Admin Admin Read-Only Org Manager Org Auditor Space Manager Space Developer Space Auditor
Scope of operation Org 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
Suspend or activate an org
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

**Not by default, unless feature flag set_roles_by_username is set to true.

*Not by default, unless feature flag user_org_creation is set to true.

Unless disabled by feature flags.

Was this helpful?
What can we do to improve?
View the source for this page in GitHub