Access control

You can share the assets or compute quota of your Earth Engine enabled project with other Earth Engine users at the project level. Earth Engine assets or compute can be shared with another user or group of users. If you want to share with a group of users, Create a new Google Group and note its email (available from the About link on the group page). This page describes how to provide access to resources, for either an individual or group and the Roles and Permissions required for different activities.

Set Earth Engine service usage

To use the Earth Engine API on a Cloud project, the API must be enabled on the project, and the user must have at least the permissions in the Earth Engine Resource Viewer role (learn more about predefined Earth Engine IAM Roles). Additionally, the user must have at least serviceusage.services.use permission on the project. That permission can be provided through the project Owner or Editor roles, or through the specific Service Usage Consumer role. An error will be thrown if the user does not have required Earth Engine permissions and Service Usage permissions on the selected project.

Set asset permissions

Set asset-level permissions

There are several options to update permissions at the asset level.

• Use the Assets Manager in the Code Editor.
• Use the Earth Engine command line.
• Use a client library, for example, ee.data.setAssetAcl().
• Or call the REST API directly.

Set project-level asset permissions

Sharing at the project level sets permissions on all assets in your Earth Engine enabled Cloud project at once.

You can share assets at the project level by assigning the appropriate Identity and Access Management (IAM) role on your project's IAM admin page. There are Predefined Earth Engine IAM Roles for sharing Earth Engine assets and resources. See Understanding Roles for a more general overview of IAM roles.

When another user attempts to access one of your assets, permissions are first checked at the asset level. If permissions have not been set at the asset level or the check fails (i.e., no access), permissions will be checked at the project level.

Set project level permissions

To set permissions at the project level, assign a project IAM role to a user or group of users:

1. Open the IAM page in the Google Cloud console
   Open the IAM Page
   Or hold the pointer over your project name on the Assets tab of the Code Editor and click the share icon.
2. Click select a project and choose your project (you should already be there if you opened the IAM page from the Code Editor).
3. Click ADD at the top and add the individual or group email as the new member, or click the edit icon next to the existing member in the project.
4. In the Role drop down search for the Earth Engine Resource role you want to grant. See Predefined Earth Engine IAM Roles for details.
5. Click the SAVE button.

VPC Service Controls

Earth Engine supports VPC Service Controls, a Google Cloud security feature which helps users secure their resources and mitigate data exfiltration risk. Adding resources to a VPC service perimeter allow for more control over data read and write operations.

Learn more about VPC-SC features and configuration.

Limitations

Enabling VPC Service Controls for your resources comes with a few limitations, for which we provided example workarounds:

Using Earth Engine with resources inside a secured VPC service perimeter is only available for Professional and Premium pricing plans. Trying to use Earth Engine API with a VPC-SC secured project associated with a Basic pricing plan will result in an error. To learn more about Earth Engine pricing visit official documentation.

More information about VPC Service Controls and its limitations can be found in Supported products and limitations.

Roles and permissions

The following sections describe the permissions and roles required to perform activities and access Earth Engine resources. See the Google Cloud documentation to learn more about Cloud project permissions and roles.

Predefined Earth Engine IAM Roles

Earth Engine provides predefined roles which allow varying degrees of control over Earth Engine resources within a project. These roles are:

Note that you may set a primitive or custom role if the predefined Earth Engine roles don't meet your needs. You can see the bundle of permissions associated with each role from the IAM Roles page by filtering to a specific role and clicking on the role.

Full access to the Earth Engine API

To give users full access to the Earth Engine service, either through the REST API directly, through the Code Editor or through a client library, users will need permission to perform operations like:

• Executing Earth Engine expressions
• Running batch computations (exports)
• Getting interactive results (online maps, thumbnails, charts, etc.)
• Creating/deleting Earth Engine assets
• Using OAuth Authentication via a Client Library to connect to Earth Engine

Asset sharing only

Grant the user one of the Predefined Earth Engine IAM Roles with minimal permissions to perform the needed activity. Note that users won't be able to consume project resources without necessary serviceusage permissions.

Project management

List and display available projects

This happens when using the Code Editor to browse available projects.

Select a project for use in the Code Editor

Create project through the Code Editor

Commercial Project Registration

The following permissions pertain to registering projects for paid use.

Commercial Earth Engine plan management

The following permissions pertain to managing Earth Engine pricing plans.

Batch task management

The following permissions pertain to configuring per-project limits on batch task concurrency. This feature is only available for commercial users of Earth Engine.

Viewing project-level batch task limits

Setting project-level batch task limits

Apps management

Display app info

Publish/Update app

Delete and app