> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Service account JSON

> Connect BigQuery to Paradime using a Google Cloud service account JSON key file for the Code IDE, Bolt production jobs, and Agent sessions.

Connect BigQuery to Paradime by uploading a service account JSON key file. Set **Target** to match the environment you are configuring (`dev`, `prod`, or `dinoai`).

<Note>
  **Available in:** Code IDE, Bolt, and Agent environments.
</Note>

<Info>
  Field access levels apply only to the **Code IDE** environment: an `Admin` sets workspace-level fields, and each developer sets their own user-level fields. In the Bolt and Agent environments, an `Admin` sets all fields.
</Info>

## Create a service account

Uploading a service account JSON key file is the quickest and most accurate way to configure a connection to BigQuery and authenticate your development credentials.

To create a service account in BigQuery, follow the detailed steps in [Google Cloud's Creating and managing service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#iam-service-account-keys-delete-console).

Grant the service account the following permissions so Paradime can read from and create tables and views in your BigQuery project:

```text theme={"system"}
BigQuery Data Editor
BigQuery User
```

## Field details

| Field                           | Description                                                                                                                                                                                                                                                                                | Example                                   |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------- |
| Profile Name                    | The profile name set in your `dbt_project.yaml`. See more [here](https://docs.getdbt.com/docs/core/connect-data-platform/connection-profiles).                                                                                                                                             | **`dbt-bigquery`**                        |
| Target                          | The target name used to identify the connection. See more [here](https://docs.getdbt.com/reference/dbt-jinja-functions/target).                                                                                                                                                            | **`dev`**                                 |
| Dataset Location                | The location of BigQuery datasets, configured using the location configuration in a BigQuery profile. Location can be either a multi-regional location (e.g. `EU`, `US`), or a regional location (e.g. `europe-west2`). See more [here](https://cloud.google.com/bigquery/docs/locations). | **`US`**                                  |
| Service Account JSON            | The service account JSON file created for this service user.                                                                                                                                                                                                                               | **`service_account_user.json`**           |
| Execution Project ID (Optional) | You can specify an Execution Project ID to bill for query execution, instead of the project where you materialize your resources. See more [here](https://docs.getdbt.com/docs/core/connect-data-platform/bigquery-setup#execution-project).                                               | (Optional) **`analytics-global-project`** |
| Dataset                         | The default dataset used to build dbt™ objects at runtime.                                                                                                                                                                                                                                 | **`dbt_john`**                            |
| Threads                         | The number of threads used in this connection. See more [here](https://docs.getdbt.com/docs/running-a-dbt-project/using-threads).                                                                                                                                                          | **`8`**                                   |


## Related topics

- [BigQuery](/integrations/bigquery/index.md)
- [GCP Secret Manager](/integrations/gcp-secret-manager.md)
- [BigQuery cost connection](/integrations/bigquery/cost-connection.md)
- [GCP Dataproc](/integrations/gcp-dataproc.md)
- [GCP Datastream](/integrations/gcp-datastream.md)