Cloud Run IAM roles

Curated roles

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

Roles can be granted to users on an entire project or on individual services. Read Managing access using IAM to learn more.

Roles only apply to Cloud Run services or jobs, they do not apply to Cloud Run domain mappings. The Project > Editor role is needed to create or update domain mappings.

Role	Description	Permissions
roles/run.admin	Can create, update, and delete services and jobs, can get, list, delete job executions. Can get and set IAM policies. Can view, apply and dismiss recommendations. Requires additional configuration in order to deploy services.	run.executions.get run.executions.list run.executions.delete run.jobs.get run.jobs.list run.jobs.create run.jobs.update run.jobs.delete run.jobs.getIamPolicy run.jobs.setIamPolicy run.services.get run.services.list run.services.create run.services.update run.services.delete run.services.getIamPolicy run.services.setIamPolicy run.routes.get run.routes.list run.routes.invoke run.configurations.get run.configurations.list run.revisions.get run.revisions.list run.revisions.delete run.locations.get run.locations.list recommender.locations.get recommender.locations.list recommender.runServiceIdentityInsights.get recommender.runServiceIdentityInsights.list recommender.runServiceIdentityInsights.update recommender.runServiceIdentityRecommendations.get recommender.runServiceIdentityRecommendations.list recommender.runServiceIdentityRecommendations.update recommender.runServiceSecurityInsights.get recommender.runServiceSecurityInsights.list recommender.runServiceSecurityInsights.update recommender.runServiceSecurityRecommendations.get recommender.runServiceSecurityRecommendations.list recommender.runServiceSecurityRecommendations.update recommender.runServiceCostInsights.get recommender.runServiceCostInsights.list recommender.runServiceCostInsights.update recommender.runServiceCostRecommendations.get recommender.runServiceCostRecommendations.list recommender.runServiceCostRecommendations.update
roles/run.developer	Can create, update, and delete services and jobs, can get, list, delete job executions. Can get but not set IAM policies. Can view, apply and dismiss recommendations.	run.executions.get run.executions.list run.executions.delete run.jobs.get run.jobs.list run.jobs.create run.jobs.update run.jobs.delete run.jobs.getIamPolicy run.services.get run.services.list run.services.create run.services.update run.services.delete run.services.getIamPolicy run.routes.get run.routes.list run.routes.invoke run.configurations.get run.configurations.list run.revisions.get run.revisions.list run.revisions.delete run.locations.get run.locations.list recommender.locations.get recommender.locations.list recommender.runServiceIdentityInsights.get recommender.runServiceIdentityInsights.list recommender.runServiceIdentityInsights.update recommender.runServiceIdentityRecommendations.get recommender.runServiceIdentityRecommendations.list recommender.runServiceIdentityRecommendations.update recommender.runServiceSecurityInsights.get recommender.runServiceSecurityInsights.list recommender.runServiceSecurityInsights.update recommender.runServiceSecurityRecommendations.get recommender.runServiceSecurityRecommendations.list recommender.runServiceSecurityRecommendations.update recommender.runServiceCostInsights.get recommender.runServiceCostInsights.list recommender.runServiceCostInsights.update recommender.runServiceCostRecommendations.get recommender.runServiceCostRecommendations.list recommender.runServiceCostRecommendations.update
roles/run.viewer	Can view services, jobs and job executions. Can get IAM policies. Can view recommendations.	run.executions.get run.executions.list run.jobs.get run.jobs.list run.jobs.getIamPolicy run.services.get run.services.list run.services.getIamPolicy run.routes.get run.routes.list run.configurations.get run.configurations.list run.revisions.get run.revisions.list run.locations.get run.locations.list recommender.locations.get recommender.locations.list recommender.runServiceIdentityInsights.get recommender.runServiceIdentityInsights.list recommender.runServiceIdentityRecommendations.get recommender.runServiceIdentityRecommendations.list recommender.runServiceSecurityInsights.get recommender.runServiceSecurityInsights.list recommender.runServiceSecurityRecommendations.get recommender.runServiceSecurityRecommendations.list recommender.runServiceCostInsights.get recommender.runServiceCostInsights.list recommender.runServiceCostRecommendations.get recommender.runServiceCostRecommendations.list
roles/run.invoker	Can invoke services and jobs.	run.jobs.run run.routes.invoke

For a reference describing the IAM permissions contained in each IAM role, refer to Cloud Run IAM Permissions.

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 services, then you must perform the additional configuration below.

Deployment permissions

A user needs the following permissions to deploy new Cloud Run services, service revisions or jobs, as noted:

• For jobs and services, iam.serviceAccounts.actAs for the Cloud Run runtime service account. By default, this is [e-mail]. The permission is typically assigned through the roles/iam.serviceAccountUser role.
• For services, run.services.create and run.services.update on the project level are required. run.services.get is not strictly required, but is recommended in order to read the status of the service. Typically assigned through the roles/run.admin role. It can be changed in the project permissions admin page.
• For jobs, run.jobs.create and run.jobs.update on the project level are required to create Cloud Run jobs with custom roles. To run existing jobs, run.jobs.run on an individual job is sufficient. run.jobs.run can be set at the job level or the project level. run.jobs.get is not strictly required, but is recommended in order to read the status of the job.

To assign the IAM Service Account User role on the Cloud Run runtime service account:

Console UI

1. Go to the Service accounts page of the Google Cloud console:

   Go to Service accounts

2. Click the email address of the Runtime Service Account ([e-mail]).

3. Click the Permissions tab.

4. Click the Grant access button.

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

6. In the Select a role dropdown, select the Service Accounts > Service Account User role.

7. Click Save.

gcloud

Use the gcloud iam service-accounts add-iam-policy-binding command, replacing the highlighted variables with appropriate values:

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

Replace PRINCIPAL with the principal you are adding the binding for, using in the form user|group|serviceAccount:email or domain:domain. For example:

• user:[e-mail]
• group:[e-mail]
• serviceAccount:[e-mail]
• domain:example.domain.com

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 Run Admin 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.

In addition to the developer needing these permissions, the Cloud Run service agent needs to be able to access the deployed container, which is the case by default.

Optional permissions for Cloud Run users

The following optional permissions can be considered when configuring accounts with minimal permission set:

• monitoring.timeSeries.list on the project level. Typically assigned through the roles/monitoring.viewer role. It allows user to access metrics generated by their service. For more information, go to the Stackdriver documentation for Access Control.
• logging.logEntries.list on the project level. Typically assigned through the roles/logging.viewer role. It allows user to access logs generated by their service. For more information, go to the Access Control guide in the Stackdriver Logging documentation.