> ## 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. # BigQuery > Paradime BigQuery Connection: Integrate BigQuery with Paradime for dbt™ projects. Ensure efficient data querying and management. Google BigQuery is a fully managed, serverless data warehouse that enables scalable analysis over petabytes of data. As a development environment in Paradime, BigQuery enables dbt™ development from Paradime's Code IDE. **IP RESTRICTIONS** Make sure to allow traffic from one of the Paradime IPs in your firewall depending on the data location selected. 👉 See also: [Paradime IP addresses](/developers/ip-restrictions). **Suggested permissions:** The following permissions will enable users in Paradime to run dbt™ from Paradime in your BigQuery project: * BigQuery Data Editor * BigQuery User *** ### Initial Setup Instructions 1. Click **Settings** in the top menu bar of the Paradime interface to access **Account Settings** 2. Click "**Connections**" in the left sidebar 3. Click "**Add New**" next to Code IDE Environment 4. Select "**BigQuery**" Next, choose your preferred authentification method to proceed: 1. [**Using BigQuery OAuth**](/products/settings/connections/development-environment/bigquery#using-bigquery-oauth) 2. [Using BigQuery Service Account JSON](/products/settings/connections/development-environment/bigquery#using-bigquery-service-account-json) *** ### Using BigQuery OAuth Follow our [BigQuery OAuth setup](/products/settings/connections/connection-security/bigquery-oauth) guide to configure OAuth authentication. Each user will need to approve the required scopes when connecting. ### Fields Details Below are list of fields and example to create a connection. **Field access levels:** * 🏢 **`Workspace level`** fields are set by the the workspace `Admin` and not configurable for by user * 👥 **`User level`** fields are set by each user (`Admin`/`Developer`) when setting the Development connection. | Field | Description | Example | Level | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------- | ------------------ | | 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`** | 🏢 Workspace level | | Target | The target name used to identify the connection. See more [here](https://docs.getdbt.com/reference/dbt-jinja-functions/target). | **`dev`** | 🏢 Workspace level | | Dataset Location | The location of BigQuery datasets can be 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`** | 🏢 Workspace level | | Project ID | The unique identifier of your BigQuery project. See more [here](https://support.google.com/googleapi/answer/7014113?hl=en). | **`dbt-demo-project`** | 🏢 Workspace level | | Client ID | The Client ID generated when setting up the OAuth credentials. | **`xyz123.apps.googleusercontent.com`** | 🏢 Workspace level | | Client Secret | The Client Secret generated when setting up the OAuth credentials. | **`GOCSPX-hPfGJe7sd238772BLBA2Bi0ds`** | 🏢 Workspace level | | 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`** | 🏢 Workspace level | | Dataset | The default dataset used to build dbt™️ objects at runtime. | **`dbt_john`** | 👥 User level | | Threads | The number of threads used in this connection. See more [here](https://docs.getdbt.com/docs/running-a-dbt-project/using-threads). | **`8`** | 👥 User level | ## Using BigQuery Service Account JSON Uploading a service account JSON key file is the quickly and accurately way to configure a connection to BigQuery and authenticate each user's 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). ### Field Details Below are list of fields and example to create a connection. **Field access levels:** * 🏢 **`Workspace level`** fields are set by the the workspace `Admin` and not configurable for by user * 👥 **`User level`** fields are set by each user (`Admin`/`Developer`) when setting the Development connection. | Field | Description | Example | Level | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------- | ------------------ | | 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`** | 🏢 Workspace level | | Target | The target name used to identify the connection. See more [here](https://docs.getdbt.com/reference/dbt-jinja-functions/target). | **`dev`** | 🏢 Workspace level | | Dataset Location | The location of BigQuery datasets can be 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`** | 🏢 Workspace level | | Service AccountService Account JSON | The service account JSON file created for this service user. | **`service_account_user.json`** | 🏢 Workspace level | | 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`** | 🏢 Workspace level | | Dataset | The default dataset used to build dbt™️ objects at runtime. | **`dbt_john`** | 👥 User level | | Threads | The number of threads used in this connection. See more [here](https://docs.getdbt.com/docs/running-a-dbt-project/using-threads). | **`8`** | 👥 User level | ## Related topics - [BigQuery](/products/settings/connections/dinoai-background-agent-environment/bigquery.md) - [Get Started](/products/radar/getting-started.md) - [Real-time Alerting](/products/radar/real-time-alerting.md) - [BigQuery Tools](/products/dino-ai/tools-and-features/warehouse-tool/bigquery-tools.md)