> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt
> Use this file to discover all available pages before exploring further.
# BigQuery
> Share your third-party risk tables into your own BigQuery dataset on a schedule, authenticated with a service account key, with a current view beside every table.
For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL.
A BigQuery destination is part of [warehouse data share](/products/warehouse-data-share). Coverbase writes through the BigQuery REST API with a service account key, creates one table per contract table on the first sync, and keeps a `_current` view beside each.
## Prepare BigQuery
1. Create a service account for Coverbase.
2. Grant it **BigQuery Data Editor** on the dataset and **BigQuery Job User** on the project.
3. Create a JSON key for the service account.
The dataset is created if it does not exist yet, in the location you give.
## Add the destination in Coverbase
1. Open **Configuration → Data Share** and click **Add destination**.
2. Choose **BigQuery**, give it a **Name**, and choose **Hourly** or **Daily**.
3. Enter the **Project ID**, **Dataset** and **Location**, and paste the **Service Account Key (JSON)**.
4. Click **Add destination**, then **Test connection**, then **Sync now**.
After saving, the card shows the service account's email as a hint. The key is never shown again. Archiving the destination deletes it.
## What lands in BigQuery
* One table per contract table, created on the first sync, with any column the contract adds later added to it.
* Each sync appends the rows that changed, stamped with `_cb_synced_at`.
* A `_current` view per table keeps the newest version of each row.
Point Looker Studio, Power BI or Tableau at the `_current` views.
## Related
Run logs, pausing and the table contract.
The Snowflake destination.
The S3 destination.
How the key is stored.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.