The following settings can be customized for the user experience in your  project. When you modify a setting, the change is immediately applied to the project. To access the page, select User menu > Admin console > Project settings.


NOTE: Users may not experience the changed environment until each user refreshes the application page or logs out and in again.

Enablement Options:

NOTE: Any values specified in this page applies exclusively to the specific project and override any system-level defaults.


OptionDescription
Default

The default value is applied. This value may be inherited from higher level configuration.

Tip: You can review the default value as part of the help text.


Enabled

The setting is enabled.

NOTE: If the setting applies to a feature, the feature is enabled. Additional configuration may be required. See below.


DisabledThe setting is disabled.
EditClick Edit to enter a specific value for the setting.

Disable Dataprep

To disable for this project, click the link.

NOTE: To remove a user and his or her assets from a project, please contact .

For more information, see Enable or Disable Dataprep.

General


Allow listing users

When enabled, individual users review and select from a list of all users in the .

NOTE: When this feature is disabled, users can access other users by providing the login email address of other users in screens such as the sharing dialogs.


Locale

Set the locale to use for inferring or validating data in the application, such as numeric values or dates. The default is United States.


NOTE: After saving changes to your locale, refresh your page. Subsequent executions of the data inference service use the new locale settings.

For more information, see Locale Settings.

Session duration

Specify the length of time in minutes before a session expires. Default is 10080 (one week).

API


Allow users to generate access tokens

When enabled, individual users can generate their own personal access tokens, which enable access to REST APIs. For more information, see Manage API Access Tokens.

Maximum lifetime for user generated access tokens (days)

Defines the maximum number of days that a user-generated access token is permitted for use in the product.

Tip: To permit generation of access tokens that never expire, set this value to -1.

For more information, see Manage API Access Tokens.


Connectivity

Custom SQL query

When enabled, users can create custom SQL queries to import datasets from relational tables. For more information, see Create Dataset with SQL.


Manage access to data using IAM permissions

When enabled, user access to data services in , such as and Bigquery, is determined by the permissions defined in a user's assigned IAM role.

NOTE: When this feature is enabled, all users that belong to the project are automatically logged out of all sessions across all projects. For example, if a user is logged into the product through another project, the user is logged out of their session when this feature is enabled. When each user logs in to the again, any changes to the user's permissions are applied. Since each each API request requires authentication in the header, API users are not automatically logged out.

For more information on IAM-based permissions, Required Dataprep User Permissions.


Flows, recipes, and plans


Column from examples

When enabled, users can access a tool through the column menus that enables creation of new columns based on example mappings from the selected column. For more information, see Overview of TBE.


Export

When enabled, users are permitted to export their flows and plans. Exported flows can be imported into other work areas or product editions. 

NOTE: If plans have been enabled in your project settings, enabling this flag applies to flows and plans.

For more information, see Export Flow.For more information, see Export Plan.

Import

When enabled, users are permitted to import exported flows and plans.

NOTE: If plans have been enabled in your project settings, enabling this flag applies to flows and plans.

For more information, see Import Flow.For more information, see Import Plan.

Plan feature

When enabled, users can create plans to execute sequences of recipes across one or more flows. For more information, see Plans Page.

For more information on plans and orchestration, see Overview of Operationalization.




Schematized output

When enabled, all output columns are typecast to their annotated types. This feature is enabled by default.




Webhooks

When enabled, webhook notification tasks can be configured on a per-flow basis in Flow View page. Webhook notifications allow you to deliver messages to third-party applications based on the success or failure of your job executions. For more information, see Create Flow Webhook Task.


Job execution


Logical and physical optimization of jobs

When enabled, the  attempts to optimize job execution through logical optimizations of your recipe and physical optimizations of your recipes interactions with data.

This workspace setting can be overridden for individual flows.

Tip: You should keep this feature enabled. Please enable it at the project level and disable it only if needed at the flow level.

For more information, see Flow Optimization Settings Dialog.

Require a companion service account for running jobs

By default, utilizes a default compute service account for running jobs on . Optionally, you can enable this feature, which requires each user in the project to provide their own companion service account to run jobs. This feature is disabled by default.

Pre-requisites:

When this feature is enabled:

When this feature is disabled:


 execution

When enabled, users can choose to execute their jobs on , a proprietary running environment built for execution of small- to medium-sized jobs in memory on the .

NOTE: Jobs executed in  are executed within the . Data is temporarily streamed to the during job execution and is not persisted.


Tip: When enabled, you can select to run jobs on Photon through the Run Jobs page. The default running environment is the one that is best for the size of your job.

When  is disabled:

For more information, see Run Job Page.


Scheduling and parameterization


Scheduling feature

When enabled, project users can schedule the execution of flows. See Add Schedule Dialog.


Experimental features

These experimental features are not supported. 

Experimental features are in active development. Their functionality may change from release to release, and they may be removed from the product at any time. Do not use experimental features in a production environment.

These settings may or may not change application behavior.

Default language

NOTE: This experimental feature is not available unless you have been provided a custom build of the for deployment. Otherwise, this setting does nothing.

Select the default language to use in the .

Language localization

NOTE: This experimental feature is not available unless you have been provided a custom build of the for deployment. Otherwise, this setting does nothing.

When enabled, the  is permitted to display text in the selected language. 

Show user language preference

NOTE: This experimental feature is not available unless you have been provided a custom build of the for deployment. Otherwise, this setting does nothing.

When enabled, users are permitted to select a preferred language in their preferences. See Preferences Page.