View Source

is a third-party service integrated with the . This section describes the requirements for enabling the product and how to disable it in your projects if needed.

Enable Dataprep

After it is authorized, only accesses project data when permitted by the user in the following ways:

Browse and preview project data
Read project data into for transformation purposes
Write results of jobs back to the project
Attach service accounts in your project to jobs used for transformation.

All project data is read from and written to user-owned projects.

NOTE: No BigQuery or Cloud Storage data is stored by or by .

bucket

When is enabled in your project, Google creates a bucket for you. Your project is automatically provisioned to use this bucket.

NOTE: This bucket is created by Google and is not under the control of . It is associated with a specific project.

NOTE: This bucket is created in a region within the United States.

During enablement in the project, you may receive a Failed: Create bucket error. If your enterprise permissions do not permit the creation of a bucket in the United States, then please create a bucket with the following naming convention:

dataprep-staging-<yourDesignation>

The designation information can be any accepted value.

Enable per Project

Access is created and enabled on a per-project basis.

Steps:

Access a project where you are the project owner.
In the Google Cloud Console, navigate to the product: https://console.cloud.google.com/dataprep.
The project owner must authorize Google to share certain customer information with :
Share account information
Click Agree and Continue.

Access to project data

The project owner must also enable access to project data:

Trifacta Dataprep > Enable or Disable Dataprep > EnableDataprep-AccessProject.png

Allow access to project data

Click Allow.

Dataprep service and roles

To enable access, Google Cloud Console creates a service account that belongs to the service and supplies it with read/write access to , , and BigQuery in the Google Cloud project. For more information, see Dataprep Roles→dataprep.serviceAgent.

IAM service accounts. The roles/dataprep.serviceAgent role that is granted during product activation includes the roles/iam.serviceAccountUser role. This role enables access to all service accounts in the project, including service accounts that may be created in the future.

For more information, see Required Dataprep User Permissions.

Launch Dataprep

After the project owner has enabled for a project, users who are granted the roles/dataprep.user role for the project can access the product.

When a user launches the product in a project for the first time, the user must complete the following:

Log in to a Google account.
Accept the Terms of Service.
Choose a bucket to use with the product.

For each project to which you have access, these steps must be performed the first time that you access the product.

Disable Dataprep

Disabling is not reversible. You cannot undo this operation.

Disabling services used by triggers the removal of all assets from the product.
All is permanently deleted and cannot be retrieved.
Services used by include (and not limited to) and Compute Engine.

Disable Dataprep for a project

When is disabled in a project, it is disabled for all users in a project. If a project owner disables :

Each project user retains access to data (including transformed data) stored within user-owned Google Cloud projects (for example, raw or transformed data stored in Cloud Storage or BigQuery)
can no longer access project data, and users can no longer view or transform project data through the product.
All metadata associated with the product is deleted. This deletion is immediate and is automatically performed by ; Google never touches this metadata. This metadata includes:
- recipes for transforming data, settings, and rules
- jobs run on project data before Dataprep was disabled (including filenames/descriptions of data)

NOTE: If you have provided with access to datasets or resources outside of the current project, disabling the product does not remove those permissions. Those permissions must be removed manually. For more information, see https://cloud.google.com/dataprep/docs/concepts/cross-bq-datasets#removing_service_account_access_to_a_bigquery_dataset.

NOTE: Disabling is permanent and irreversible.

NOTE: When you disable the product in your project, the bucket associated with the product is untouched. That data remains.

Steps to disable through for the current project:

In the menu in the , select User menu > Admin console > Project settings. For more information, see Dataprep Project Settings Page.
In the Project Settings page, click Disable Dataprep.
This link redirects you to the Google Console.
In the Google Console URL, verify that the project for which you wish to disable is selected.
You can navigate to the following location: https://console.cloud.google.com/dataprep/revokeAccess
The following dialog is displayed:
Disable Dataprep in this project
To disable use of in the selected project, click Disable.
This step cannot be undone.
The product is disabled for your project.

Disable billing in Marketplace

If you are no longer using the at all, you must disable it through the Marketplace.

You will continue to be billed for the Service according to the terms of your contract until the Service is disabled in the Marketplace.

For more information, see https://console.cloud.google.com/marketplace/product/endpoints/cloud-dataprep-editions-v2.

Forced Cancellations

Some changes to the billing for your project have been known to cause cancellations of in your project. These cancellations are submitted from Google, Inc. to without additional information.

NOTE: If you have received an unexpected cancellation of for a project, please contact Google Support.

Typically, the solution is to re-enable the product for your project.