Skip to main content
AskTable connects to Google BigQuery with a Service Account key. There are two steps: create a service account with read-only permissions in Google Cloud and download its JSON key, then paste the key into AskTable.

​
1. Create a Service Account key

1

Open the service accounts page

Open the Google Cloud Console, select the target project at the top, go to IAM & Admin → Service Accounts, click Create Service Account, and give it a name (for example, asktable-readonly).
2

Grant BigQuery permissions

Grant the service account the following two roles — the minimum required for AskTable’s read-only queries:To expose only specific datasets, skip the project-level Data Viewer role: in the BigQuery console, click Share → Add Principal on the target dataset and grant Data Viewer to the service account there. Job User still needs to be granted at the project level.
3

Create a JSON key

Open the service account you just created, switch to the Keys tab, click Add Key → Create new key, and choose JSON. Your browser downloads a .json key file — this file is the only credential you need for the next step.
Two situations prevent key creation: BigQuery sandbox projects (without billing enabled) do not support service account keys, and some organization policies (iam.disableServiceAccountKeyCreation) disable key creation — contact your Google Cloud administrator if you hit an error.

​
2. Connect in AskTable

In the left main navigation, click More, then click Data Sources in the data workspace sidebar and click Add Data in the top right. Under the Big Data category, select Google BigQuery and fill in the connection details: There is no host, port, or project ID to fill in — AskTable detects the GCP project from the key automatically. Click Add Now. AskTable tests the connection automatically. On success, you proceed to table selection — BigQuery datasets appear as the schema level there.
The key is stored encrypted in AskTable and is never echoed back by any page or API. To rotate the key later, paste a new one in the connection settings on the data source detail page; leaving it blank keeps the current key unchanged.

​
Troubleshooting

​
Next steps