Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.summation.com/llms.txt

Use this file to discover all available pages before exploring further.

Summation reads from BigQuery as a Google Cloud service account. You configure the project to bill jobs to and paste the service account’s JSON key.

​
What you’ll need

Grant bigquery.dataViewer on individual datasets rather than at the project level to limit Summation’s read scope to exactly what you intend.

​
Form fields

FieldRequiredStored asNotes
Project IDYesConfigThe GCP project Summation runs jobs in, e.g. my-gcp-project-123. See Identifying projects.
Dataset IDOptionalConfigDefault dataset to scope the connection to. Leave blank to expose multiple datasets. See Datasets overview.
LocationOptionalConfigBigQuery region, e.g. US, EU, us-east4. Required when datasets aren’t in the multi-region default. See Dataset locations.
Service Account JSONYesSecretThe full contents of the JSON key file (including the surrounding { and }).

​
Creating the service account

PROJECT_ID=my-gcp-project-123

gcloud iam service-accounts create summation \
  --project="$PROJECT_ID" \
  --display-name="Summation"

# Lets Summation run queries in the project
gcloud projects add-iam-policy-binding "$PROJECT_ID" \
  --member="serviceAccount:summation@$PROJECT_ID.iam.gserviceaccount.com" \
  --role="roles/bigquery.jobUser"

# Repeat per dataset you want to expose
bq add-iam-policy-binding \
  --member="serviceAccount:summation@$PROJECT_ID.iam.gserviceaccount.com" \
  --role="roles/bigquery.dataViewer" \
  "$PROJECT_ID:analytics"

# Generate a JSON key — paste this into the form, then delete the local copy
gcloud iam service-accounts keys create summation-key.json \
  --iam-account="summation@$PROJECT_ID.iam.gserviceaccount.com"
The downloaded summation-key.json is a credential. Paste it into Summation, then delete the local copy. See Best practices for managing service account keys.

​
Adding datasets

After saving the connection, browse the project’s BigQuery datasets and select tables or views. Source references use the form: 
adbc:dataset_id.table_name

​
Common problems

Error or symptomLikely cause
Access Denied: Project ... User does not have bigquery.jobs.create permissionGrant roles/bigquery.jobUser on the project.
Not found: Dataset ...The Location doesn’t match the dataset’s region. BigQuery rejects cross-region reads. See Dataset locations.
Invalid JSONPaste the full file contents including the surrounding { and }. Don’t escape or wrap the JSON.