...
| Permission | Product Use |
|---|
| bigquery.tables.delete | If this permission is not granted to a user, that user requires one of the following permissions to drop or truncate table data in BigQuery: - The user is granted
editor or owner role on the project. - The user is granted bigquery.tables.delete for the project.
| Info |
|---|
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. |
|
BigQuery job execution
To enable execution of jobs in BigQuery, the following permission must be enabled. Additional configuration may be required. For more information on this feature, see BigQuery Running Environment.
| Permission | Product Use |
|---|
| bigquery.jobs.create | This permission enables execution of jobs within BigQuery. It is also used for custom SQL queries, which is enabled by default. In most projects, this permission is enabled by default. |
BigQuery job execution on
filesIf you have enabled execution of jobs in BigQuery, you can extend that capability to execute jobs for data sources hosted in
. GCS execution in BigQuery requires that external tables be enabled in BigQuery. The following permissions are required to create and use external tables.| Tip |
|---|
Tip: In most projects, these permissions are enabled by default. |
- For more information on these permissions, see https://cloud.google.com/bigquery/external-data-cloud-storage#permissions.
- Additional configuration may be required. For more information on this feature, see BigQuery Running Environment.
| Permission | Product Use |
|---|
bigquery.tables.create | Enabled in the default role. |
| bigquery.tables.getData | Enabled in the default role. |
| bigquery.jobs.create | Required for job execution in BigQuery. See previous section. |
Google Sheets access
| D s ed |
|---|
| r | true |
|---|
| editions | gdpent,gdppro,gdpsta,gdppr,gdpst |
|---|
|
...
