Cloud Functions IAM Roles

Curated roles

The following table describes Identity and Access Management (IAM) roles that are associated with Cloud Functions, and lists the permissions that are contained in each role.

Roles can be granted to users on an entire project or on individual functions.

Role	Description	Permissions
roles/cloudfunctions.developer	Can create, update, and delete functions. Can't set IAM policies but can view source code. Requires additional configuration in order to deploy functions.	cloudfunctions.functions.call cloudfunctions.functions.create cloudfunctions.functions.delete cloudfunctions.functions.get cloudfunctions.functions.invoke cloudfunctions.functions.list cloudfunctions.functions.update cloudfunctions.functions.sourceCodeGet cloudfunctions.functions.sourceCodeSet cloudfunctions.operations.get cloudfunctions.operations.list cloudfunctions.locations.list resourcemanager.projects.get servicemanagement.projectSettings.get serviceusage.services.get
roles/cloudfunctions.viewer	Can view functions. Can't get IAM policies or view source code.	cloudfunctions.functions.get cloudfunctions.functions.list cloudfunctions.operations.get cloudfunctions.operations.list cloudfunctions.locations.list resourcemanager.projects.get servicemanagement.projectSettings.get serviceusage.services.get

Custom roles

For developers that want to define their own roles containing bundles of permissions that they specify, IAM offers custom roles.

If the role contains permissions that let a developer deploy functions, then you must perform the additional configuration below.

Additional configuration for deployment

In order to assign a user the Cloud Functions Developer role (roles/cloudfunctions.developer) or a custom role that can deploy functions, you must also assign the user the IAM Service Account User role (roles/iam.serviceAccountUser) on the Cloud Functions Runtime service account.

Caution: Assigning the IAM Service Account User role indirectly grants the role associated with the runtime service account to the user. For example: a user has the Cloud Functions Developer role, and the user is also assigned the role of IAM Service Account User on a runtime service account. If the runtime service account has the Editor role, the user can then "act as" an Editor. We recommend configuring the runtime service account for least privilege to minimize the impact of these role assignments.

Console

1. Go to the Google Cloud Platform Console:

   Go to Google Cloud Platform Console

2. Select the Runtime Service Account ([e-mail]) from the table.

3. Click Show Info Panel in the top right corner to show the Permissions tab.

4. Click the Add member button.

5. Enter the member (e.g. user or group email) that that matches the member you're granting the Admin or Developer role to.

6. Grant the roles/iam.serviceAccountUser role under Service Accounts > Service Account user in the Select a role dropdown.

7. Click Save.

GCloud

1. Use the gcloud iam service-accounts add-iam-policy-binding command, replacing [VALUES_IN_BRACKETS] with appropriate values:

gcloud iam service-accounts add-iam-policy-binding \
  [e-mail] \
  --member="[MEMBER]" \
  --role="roles/iam.serviceAccountUser"