Access Control for Projects using IAM

Google Cloud Platform offers Identity and Access Management (IAM), which lets you give more granular access to specific Google Cloud Platform resources and prevents unwanted access to other resources. IAM lets you adopt the security principle of least privilege, so you grant only the necessary access to your resources.

IAM lets you control who (users) has what access (roles) to which resources by setting IAM policies. IAM policies grant specific role(s) to a user giving the user certain permissions.

This page explains the Identity and Access Management (IAM) roles that are available at the project level. For a detailed description of Cloud IAM, read the IAM documentation. In particular, see Granting, Changing, and Revoking Access.

Permissions and roles

With Cloud IAM, every Google Cloud Platform method requires that the account making the API request has appropriate permissions to access the resource. Permissions allow users to perform specific actions on Cloud resources. For example, the resourcemanager.projects.list permission allows a user to list the projects they own, while resourcemanager.projects.delete allows a user to delete a project.

The following table lists the permissions that the caller must have to call a projects API:

Method Required Permission(s)
resourcemanager.projects.create() resourcemanager.projects.create
resourcemanager.projects.delete() resourcemanager.projects.delete
resourcemanager.projects.get() resourcemanager.projects.get
resourcemanager.projects.getIamPolicy() resourcemanager.projects.getIamPolicy
resourcemanager.projects.list() Does not require any permission. The method lists projects for which the caller has resourcemanager.projects.get permission. If you provide a filter while calling list(), for example, byParent, the method lists projects for which you have the resourcemanager.projects.get permission and which satisfies the filter condition.
resourcemanager.projects.setIamPolicy() resourcemanager.projects.setIamPolicy
resourcemanager.projects.testIamPermissions() Does not require any permission.
resourcemanager.projects.undelete() resourcemanager.projects.undelete
resourcemanager.projects.update() To update a project's metadata, requires resourcemanager.projects.update permission. To update a project's parent and move the project into an organization, requires resourcemanager.projects.create permission on the organization.

You don't directly give users permissions; instead, you grant them roles, which have one or more permissions bundled within them.

You can grant one or more roles on the same project. When using the resourcemanager.projects.getIamPolicy() method to view permissions, only the permissions assigned to the project itself will appear, not any inherited permissions.

Using Predefined Roles

The following table lists the roles that you can grant to access a project, the description of what the role does, and the permissions bundled within that role.

Role Description Permissions
roles/owner Full access to all resources. All permissions for all resources.
roles/editor Edit access to all resources. Create and update access for all resources.
roles/viewer Read access to all resources. Get and list access for all resources.
roles/browserBeta Access to browse resources in the project.
  • resourcemanager.organizations.get
  • resourcemanager.projects.get
  • resourcemanager.projects.getIamPolicy
  • resourcemanager.projects.list
  • resourcemanager.projectInvites.get

Creating Custom Roles

In addition to the predefined roles described in this topic, you can also create Custom Roles that are collections of permissions that you tailor to your needs. When creating a Custom Role for use with Resource Manager, be aware of the following points:
  • List and get permissions, such as resourcemanager.projects.get/list, should always be granted as a pair.
  • When your Custom Role includes the folders.list and folders.get permissions, it should also include projects.list and projects.get.
  • Be aware that the setIamPolicy permission for organizations, folders, and projects allows the user to grant all other permissions, and so should be assigned with care.

Access control at the project level

You can grant roles to users at the project level using the Google Cloud Platform Console, the Resource Manager API, and the gcloud command-line tool. For instructions, see Granting, Changing, and Revoking Access to Project Members.

Default roles

When you create a project, you are granted the roles/owner role for the project to provide you full control as the creator. See above for the permissions that this role provides. This default role can be changed as normal in an Cloud IAM policy.

Was this page helpful? Let us know how we did:

Send feedback about...

Resource Manager Documentation