How to Configure Make Bigquery Permissions
To set up make bigquery permissions, grant a Google Cloud role to your account. Then connect that account to Make using OAuth or a service key. Many teams assign a project editor or admin role to get workflows running fast. This broad setup gives every automation scenario full read and write power over tables. One bad workflow change can expose sensitive rows or alter production records. How make bigquery permissions work in Google Cloud Make talks to Google BigQuery through the official Goog
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
To set up make bigquery permissions, grant a Google Cloud role to your account. Then connect that account to Make using OAuth or a service key. Many teams assign a project editor or admin role to get workflows running fast. This broad setup gives every automation scenario full read and write power over tables. One bad workflow change can expose sensitive rows or alter production records.
How make bigquery permissions work in Google Cloud
Make talks to Google BigQuery through the official Google Cloud API. Every API call needs two layers of permission to succeed. First, the user or service account needs a Google Cloud IAM role. Second, the connection needs the right OAuth scope to act on your behalf.
Inside BigQuery, IAM roles control two main tasks. One task is running a query job at the project level. The other task is reading or writing table data at the dataset level. If your account only has dataset read rights, it cannot run a query job. If it only has job rights, it cannot read the rows inside a table.
You must combine a job user role with a data viewer or editor role. Teams apply the data role to a single dataset instead of the whole project. This setup keeps Make from reading unrelated tables in other datasets. When you link a user account in Make, Google asks for OAuth consent. When you use a service account, you upload a key file to the app.
Choosing between user logins and service keys
Make lets you log in with a personal Google account or a service account. Personal accounts are fast to set up during early testing. Still, the workflow inherits every table right that the human user holds. If that person leaves the company, the automation breaks right away.
Service accounts work better for shared team workflows. You create a dedicated identity in Google Cloud just for Make. Then you attach only the specific dataset roles that the workflow needs. Even with a service account, static key files create a real risk. Anyone who copies that key file can run queries from outside your network. Teams must rotate these keys on a schedule and watch audit logs for abuse.
BigQuery IAM + AI Agent Permissions: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native roles solve and what they leave open
Native Google Cloud roles decide who can log in and which datasets they see. Scoping roles to one dataset stops a workflow from touching your other warehouse tables. It also separates read tasks from write tasks across different Make scenarios.
Still, static roles cannot inspect the actual SQL text that Make sends in flight. Once a role grants read rights on a table, every column is open by default. A flawed scenario can pull emails, phone numbers, card numbers, or national IDs. Native IAM also cannot require a quick human check before a destructive query runs. To control individual statements and mask sensitive fields in results, teams need runtime controls.
Add runtime guardrails and masking beside your databases and APIs
Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits beside the service as an open-source proxy, a sidecar for your database or API.
Before a query runs, hoop.dev guardrails check the statement against your rules. An AI Analyzer you configure can score intent or hold risky calls for human review. Next, hoop.dev data masking rewrites sensitive fields in responses, and each verdict is logged per listener. Explore the MIT-licensed project on GitHub.
Frequently asked questions
Why does Make fail to run a query when it has data viewer rights?
Data viewer rights only let the account read table rows. You must also grant a job role at the project level to run queries.
Should I use a personal Google login or a service account for Make?
Use a dedicated service account for any shared or production workflow. Personal logins tie the automation to one employee and often carry too many rights.
Can BigQuery IAM roles hide sensitive columns from Make workflows?
Standard dataset roles apply to whole tables, not specific fields inside a query result. Hiding emails or card numbers requires extra policy tags or runtime data masking.
Related guides
In this post