# Access control with IAM (1st gen)

You (that is, the user or service account deploying the function) can set access
control using roles at the project level. Grant a role to a
project member or service account to determine the level of access to your
Google Cloud project and its resources. By default, all Google Cloud projects come
with a single user: the original project creator. No other users have access to
the project, and therefore, access to functions, until a user is added as a
project team member.

## Access control for users

You can add users as team members to your project and grant them roles using
[Identity and Access Management (IAM)](https://docs.cloud.google.com/iam/docs/overview.md.txt).

Cloud Run functions supports the
[basic roles](https://docs.cloud.google.com/iam/docs/understanding-roles#bas8c) of **Editor** ,
**Owner** , and **Viewer**, which give the following permissions:

- **Editor** and **Owner**: Read and write access to all functions-related resources. Lets users deploy, update, and delete functions. Additional access to other resources in the project.
- **Viewer**: Read-only access to functions and locations. Lets users list functions and see their details, but does not let them view the source code. Additional access to other resources in the project.

Cloud Run functions also supports the Cloud Run functions
[predefined **Developer** and **Viewer** roles](https://docs.cloud.google.com/functions/docs/reference/iam/roles.md.txt),
which give the following permissions:

- **Developer**: Read and write access to all functions-related resources. Lets users deploy, update, and delete functions. No access to other resources in the project.
- **Viewer**: Read-only access to functions and locations. Lets users list functions and see their details, but does not let them view the source code. No access to other resources in the project.

> [!NOTE]
> **Note:** To write or access Cloud Run functions logs, a project member must also have the appropriate logging permissions. For more information, see the [Cloud Logging access control guide](https://docs.cloud.google.com/logging/docs/access-control.md.txt).

## Access control for service accounts

A
[service account](https://docs.cloud.google.com/iam/docs/service-account-types.md.txt) is a special type of
Google Cloud account that acts as an identity for a non-human user that needs to
authenticate and be authorized to access data and perform various actions. Some
of these accounts are
[created and managed by Google itself](https://docs.cloud.google.com/iam/docs/service-account-types.md.txt#google-managed)
and are known as
[*service agents*](https://docs.cloud.google.com/iam/docs/service-agents.md.txt).

The following service accounts are used for Cloud Run functions:

| Name | Member ID | Role |
|---|---|---|
| App Engine default service account | `PROJECT_ID@appspot.gserviceaccount.com` | Editor |
| Google Cloud Run functions Service Agent | `service-PROJECT_NUMBER@gcf-admin-robot.iam.gserviceaccount.com` | Cloud Run functions Service Agent |
| --- | `PROJECT_NUMBER@cloudbuild.gserviceaccount.com` | Cloud Build Service Account |
| Cloud Build Service Account | `service-PROJECT_NUMBER@gcp-sa-cloudbuild.iam.gserviceaccount.com` | Cloud Build Service Agent |
| Google Container Registry Service Agent | `service-PROJECT_NUMBER@containerregistry.iam.gserviceaccount.com` | Container Registry Service Agent |
| Artifact Registry Service Agent | `service-PROJECT_NUMBER@gcp-sa-artifactregistry.iam.gserviceaccount.com` | Artifact Registry Service Agent |

### Runtime service accounts

At runtime, Cloud Run functions defaults to using the App Engine
default service account (`PROJECT_ID@appspot.gserviceaccount.com`), which has
the **Editor** role on the project. You can change the role of this service
accounts to limit or extend the permissions for your running functions. You can
also change which service account is used by
[providing a non-default individual service account](https://docs.cloud.google.com/functions/1stgendocs/securing/function-identity.md.txt#individual).

To learn more about service accounts, see the
[service accounts documentation](https://docs.cloud.google.com/iam/docs/understanding-service-accounts).

> [!NOTE]
> **Note:** Authenticating as the runtime service account from inside your function might fail if you change the Cloud Run functions service account's permissions.

### Administrative service accounts

To perform administrative actions on your project during the creation,
updating, or deletion of functions, all projects in Cloud Run functions
require the Google Cloud Run functions Service Agent service account
(`service-PROJECT_NUMBER@gcf-admin-robot.iam.gserviceaccount.com`).

In addition, all runtimes carry out container image building and storage within
your project. To support this, you also need to provision the following:

- The basic [Cloud Build service account](https://docs.cloud.google.com/build/docs/cloud-build-service-account.md.txt) (`PROJECT_NUMBER@cloudbuild.gserviceaccount.com`)
- The [Cloud Build Service Agent service account](https://docs.cloud.google.com/iam/docs/service-agents.md.txt#cloud-build-service-agent) (`service-PROJECT_NUMBER@gcp-sa-cloudbuild.iam.gserviceaccount.com`)
- The [Google Container Registry Service Agent service account](https://docs.cloud.google.com/container-registry/docs/overview#container_registry_service_account) (`service-PROJECT_NUMBER@containerregistry.iam.gserviceaccount.com`)

These service accounts should have the roles listed in the earlier
[table](https://docs.cloud.google.com/functions/1stgendocs/concepts/iam.md.txt#roles).

#### Google Cloud Run functions Service Agent service account

By default, the Google Cloud Run functions Service Agent service account
(`service-PROJECT_NUMBER@gcf-admin-robot.iam.gserviceaccount.com` has
the **cloudfunctions.serviceAgent** role on your project.

> [!WARNING]
> **Warning:** If you remove the default role binding or modify the permissions granted to the Cloud Run functions Service Agent service account on your Google Cloud project, the Cloud Run functions create, update, and delete operations might fail.

Here's a few of the notable permissions that the `cloudfunctions.serviceAgent`
uses:

| Permission | Description |
|---|---|
| `roles/artifactregistry.admin` | Manage repositories and store build images in Artifact Registry. |
| `roles/cloudbuild.builds.editor` | Required to use Cloud Build to perform builds in user project. |
| `roles/cloudbuild.customworkers.builder` | Create builds in Cloud Build custom workers. |
| `cloudfunctions.functions.invoke` | Invoke an IAM-guarded HTTP function. |
| `compute.globalOperations.get`, `compute.networks.access`, `vpcaccess.connectors.{get, use}` | Provision functions with access to the consumer projects VPC. |
| `firebasedatabase.instances.{get, update}` | Create functions triggered by the Firebase Realtime Database. |
| `iam.serviceAccounts.{actAs, getAccessToken, signBlob}` | Ability to get runtime service account credentials. |
| `iam.serviceAccounts.getOpenIdToken` | Needed for the agent to get an OpenID token on a user-specified authority. OpenID token is used for invoking IAM-enabled functions. |
| `pubsub.subscriptions` | Manage subscriptions in the user's project. |
| `pubsub.topics` | Manage topics in the user's project. |
| `storage.buckets.{get, update}` | Configure notifications on a Cloud Storage bucket that trigger a function. |
| `storage.buckets.create`, `storage.objects.{delete, get, create, list}` | Required for storing source code in user project. |

You can see the entire set of permissions under the [predefined IAM roles](https://docs.cloud.google.com/iam/docs/roles-permissions/cloudfunctions.md.txt#cloudfunctions.serviceAgent)
or by running this command:

```bash
gcloud iam roles describe roles/cloudfunctions.serviceAgent
```

<br />

You can reset this service account to the default role by removing whatever role
it has and adding the Cloud Run functions Service Agent role:

```bash
gcloud projects add-iam-policy-binding PROJECT_ID \
  --member serviceAccount:service-PROJECT_NUMBER@gcf-admin-robot.iam.gserviceaccount.com \
  --role roles/cloudfunctions.serviceAgent
```

## Troubleshooting permission errors

If you get permission errors when you deploy, update, delete, or execute
functions in your project, perform the following steps:

1. Make sure that you have the **Editor** or **Owner** role on your project, or
   that you are using the **Cloud Run functions Developer** role.

   If you are using the **Cloud Run functions Developer** role at the project
   level, also ensure that you have
   [granted the user the **IAM Service Account User** role](https://docs.cloud.google.com/functions/docs/reference/iam/roles.md.txt#additional-configuration).

   Only execution permissions are allowed at the per-function level.
2. Verify that the Cloud Run functions Service Agent service account
   (`service-PROJECT_NUMBER@gcf-admin-robot.iam.gserviceaccount.com`) has the
   **cloudfunctions.serviceAgent** role for your project.

   Make sure the **Include Google-provided role grants** box on the
   **Permissions** tab of the [Console IAM](https://console.cloud.google.com/iam-admin/iam/) page
   is checked to see this account. Or you can use
   `gcloud projects add-iam-policy-binding PROJECT_ID`.
3. Ensure that you have permissions for trigger sources, such as
   [Pub/Sub](https://docs.cloud.google.com/functions/1stgendocs/calling/pubsub.md.txt) or
   [Cloud Storage](https://docs.cloud.google.com/functions/1stgendocs/calling/storage.md.txt).

If you get an "insufficient permissions" error, or have other
authentication problems when you run your functions, make sure that the runtime
service account has the correct permissions to access the resources your
functions need. Then, repeat steps 2 and 3.

If you get a "service unavailable" error during deployment, make
sure that the runtime service account `PROJECT_ID@appspot.gserviceaccount.com`
exists in your project. To recreate this service account if it was deleted, see
[Undeleting a service account](https://docs.cloud.google.com/iam/docs/service-accounts-delete-undelete.md.txt#undeleting).

See also [Troubleshooting Cloud Run functions](https://docs.cloud.google.com/functions/1stgendocs/troubleshooting.md.txt).