Access Control

Beta

This is a beta release of Google Cloud Functions. This API might be changed in backward-incompatible ways and is not subject to any SLA or deprecation policy.

You can set access control using roles at the project level. Assign a role to a project member or service account to determine the level of access to your Google Cloud Platform project and its resources. By default, all Google Cloud Platform 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 assign them roles using Identity and Access Management (IAM).

Cloud Functions supports the primitive roles Editor, Owner, and Viewer, which grant the following permissions:

• Editor and Owner: Read and write access to all functions-related resources. Allows users to deploy, update, and delete functions.
• Viewer: Read-only access to functions and locations. Allows users to list functions and see their details, but does not allow them to view the source code.

Runtime service account

At runtime, Cloud Functions uses the service account [e-mail], which has the Editor role on the project. You can change the roles of this service account to limit or extend the permissions for your running functions.

To learn more about service accounts, see the Service Accounts documentation.

Google APIs service account

For administrative actions on your project during the creation, updating, or deletion of functions, the Cloud Functions service uses the Google APIs service account [e-mail]. By default, this service account has the Editor role on your project. Creating, updating, and deleting functions may fail if you reduce this account's permissions.

An example of an administrative action is creating a internal subscription to a Pub/Sub topic when you deploy a function triggered by that topic.

Troubleshooting permission errors

If you get permission errors when you deploy, update, or delete functions in your project, make sure that:

• You have the Editor or Owner role on your project.
• The Google APIs service account ([e-mail]) has the Editor role on your project.
• You have permissions for trigger sources, such as Pub/Sub or the Cloud Storage bucket triggering your function.

If you get an ”insufficient permissions” error when you run your functions, make sure that the [e-mail] service account has the correct permissions.