In the Identity and Access Management (IAM) allows you to control user and group access to your project's resources. This section describes the IAM permissions relevant to  and the IAM roles that grant those permissions. To access the IAM console, see

For more information on the service accounts used by  to manage security and permissions while running  jobs, see

Tools for manage IAM policies:

For more information, see

Required Roles and Their Permissions

To use , the following roles are required. Below, you can review each required role, its purpose, and the permissions that are enabled by it.

RoleUsePermissions and roles

Enables a user to run in a project See below.


  • dataprep.projects.use

Enables the platform to access and modify datasets and storage and to run and manage jobs on behalf of the user within the project

NOTE: When the product is enabled within a project, this role is granted by the project owner as part of the enablement process. For more information, see Enable or Disable Dataprep.


  • storage.buckets.get
  • storage.buckets.list


  • roles/dataflow.developer
  • roles/bigquery.user
  • roles/bigquery.dataEditor
  • roles/storage.objectAdmin
  • roles/iam.serviceAccountUser

roles/dataprep.user IAM Role

All users of any version of  must be assigned the roles/dataprep.user IAM Role.

This role and its related permissions enable access to all data in a project. Other permissions do not apply.

Required Permissions for 

The following base set of IAM permissions and some additional permissions are required for accessing the product. Below, you can review the required permissions for this product edition.

NOTE: These permissions provide basic access to the . Additional features within the product or available through external integrations are considered optional.


PermissionProduct Use

Allow a user to use


Get project details

Run  on :

PermissionProduct Use

List available machine types for jobs

Create a job

List jobs


Get job details


Get job details

Read and write to , the base storage for :

PermissionProduct UseRequirement

List buckets in project

Required at project level
storage.buckets.getGet bucket metadataRequired for staging bucket only
storage.objects.createCreate filesRequired for staging bucket only
storage.objects.deleteDelete filesRequired for staging bucket only
storage.objects.getRead filesRequired for staging bucket only
storage.objects.listList filesRequired for staging bucket only

Optional Permissions

Permissions required to integrate with external services are considered optional. 


Read and write to BigQuery, including views and custom SQL:

PermissionProduct UseRequirement

For Custom SQL query support and launching jobs with BigQuery data sources.

Required at project level to use BigQuery
bigquery.datasets.getList and get metadata about datasets in projectCan be applied at project level or at individual dataset level
bigquery.tables.createExecute custom queriesCan be applied at project level or at individual dataset level
bigquery.tables.getCreate tables in datasetCan be applied at project level or at individual dataset level
bigquery.tables.getGet table metadataCan be applied at project level or at individual dataset level
bigquery.tables.getDataget table contentsCan be applied at project level or at individual dataset level
bigquery.tables.listList tables in datasetCan be applied at project level or at individual dataset level

Feature Permissions

Additional permissions may be required to use specific features. Individual users may be required to permit  access when the feature is first used. 

 job cancellation

PermissionProduct Use users to cancel their jobs in progress. It is not required for the product to work but may be helpful to add via IAM roles.

BigQuery publishing options

The following permissions are required to publish to BigQuery:

PermissionProduct Use
bigquery.datasets.createCreate datasets in BigQuery
bigquery.datasets.updateUpdate datasets in BigQuery

The following permission is not required to publish to BigQuery.

PermissionProduct Use

If this permission is not granted to a user, that user can drop or truncate table data in BigQuery, only if one of the following permissions is enabled in a user's account: 

  • The user is granted editor or owner role on the project.
  • The user is granted bigquery.tables.permission for the project.

NOTE: If a user does not have this permission when publishing to a table, the user receives a warning that the target dataset is read-only.

Google Sheets access

For more information, see Import Google Sheets Data.

Additional Permissions for Cloud IAM

In addition to the IAM roles above, users must also be granted the following to enable data access based on their Cloud IAM:

These permissions ensure that users can access the appropriate data within .