Controlling access to repositories

Access control in Google Cloud Platform is controlled using Cloud Identity and Access Management (Cloud IAM). Cloud IAM allows you to set permissions specifying who has what kind of access to which resources in your project.

Google Cloud Source Repositories uses IAM for access control. You can use IAM to add team members to your project and to grant them permissions to create, view, and update repositories.

This page explains describes the IAM permissions and roles that apply to Cloud Source Repositories.


With IAM, every action on a repository in Cloud Source Repositories requires that the account initiating the action has the appropriate permissions. You do not grant specific permissions to an account. Instead, you grant a role that contains the appropriate set of permissions.

The following table describes the permissions available in Cloud Source Repositories.

Permission Description
source.repos.list List repositories within the project.
source.repos.create Create a new repository within the project.
source.repos.get Clone, fetch, browse on the web.
source.repos.update Push new changes to the repository.
source.repos.delete Delete repository.
source.repos.getIamPolicy Read/view the IAM policy of a repository.
source.repos.setIamPolicy Change the IAM policy of a repository.


You assign permissions to accounts through the use of roles. The following table lists the roles available for Cloud Source Repositories.

Role Role Title
role/source.reader Source Repository Reader
role/source.writer Source Repository Writer
role/source.admin Source Repository Administrator

Roles and permissions matrix

Use the table below to select the appropriate role for an account, based on the types of actions you want that account to perform.

Capability reader writer admin
List repositories
Clone, fetch and browse repositories
Update repositories
Create repositories
Delete repositories
View IAM policies
Set IAM policies

Custom roles

In addition to the predefined roles, Cloud Source Repositories also supports custom roles. For more information, see Creating and Managing Custom Roles in the Cloud IAM documentation.

Granting member access

In Google Cloud IAM, you grant access to members. There are multiple types of members. For a complete list, see Concepts related to identity.

You cannot make a GCP repository public. As a result, Cloud Source Repositories does not support the following member types:

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

Send feedback about...

Cloud Source Repositories