How to Configure Make Bigquery Read Only Access

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up make bigquery read only access by pairing a viewer role with a service key. You then add that key to your Make scenario so it can run safe queries. Many teams skip this step and use an owner account for speed. That broad role lets a broken workflow change or drop live tables by mistake. How to set up make bigquery read only access in Google Cloud Start inside your Google Cloud project where your data lives. Create a new service account just for your Make scenarios. Never share one

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.

You set up make bigquery read only access by pairing a viewer role with a service key. You then add that key to your Make scenario so it can run safe queries. Many teams skip this step and use an owner account for speed. That broad role lets a broken workflow change or drop live tables by mistake.

How to set up make bigquery read only access in Google Cloud

Start inside your Google Cloud project where your data lives. Create a new service account just for your Make scenarios. Never share one service account across different apps or teams. Next, assign two core rights to this account. First, give the account the right to start query jobs in the project. Second, grant the account viewer rights on the specific dataset it needs.

A viewer role without job rights cannot run a query at all. Job rights let the account use compute power to scan tables. Viewer rights let the account read the rows inside those tables. Keep these viewer rights on one dataset instead of the whole project. This limits what the workflow can read if someone steals the key.

Once the roles are set, create a key file for the service account. Upload this key into Make when you build your database module. Test the setup by running a small select query on a sample table. Check the project logs to confirm the service account ran the job.

Why dataset viewer roles need extra query controls

Native cloud roles do a great job of blocking write commands. A workflow with viewer rights cannot delete rows or drop tables. It also cannot change table schemas or add new columns. This stops a bad scenario from wrecking your main data store.

Still, native viewer roles only check who logs in to the database. They do not inspect what individual queries do while they run. A read query can still pull millions of rows at once. That single run can spike your cloud bill in seconds. Worse, a scenario can pull sensitive fields and send them to outside apps.

Auditor Read-Only Access + Customer Support Access to Production: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

For example, a table might hold customer emails, phone numbers, or card numbers. A basic viewer role lets Make read every column in that table by default. If the scenario sends query results to a chat tool, private data leaks out. Cloud roles cannot rewrite those sensitive fields in results on the fly.

Ways to keep automated data workflows safe

Teams can reduce risk by creating clean views for automation tools. A view can leave out columns with national IDs or card numbers. You then grant the Make service account viewer rights on the view alone. The account never gets rights on the raw base table.

You should also set query size limits on the cloud project. These limits stop a bad loop in Make from scanning terabytes of data. Finally, rotate your service account keys on a fixed schedule. Delete old keys right away so leaked files cannot log in.

Govern statements and responses across databases and APIs

Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.

First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.

Frequently asked questions

Why does my read only service account fail to run queries?

Reading data in BigQuery requires two separate permissions. Your account needs viewer rights on the data and job rights on the project. Without job rights, the account cannot start the query engine.

Can I limit Make to read only one table instead of a dataset?

Yes, you can grant viewer roles at the single table or view level. Skip the dataset role and apply the viewer permission directly to that one table. The service account will not see any other tables in the dataset.

How do I stop Make from pulling sensitive columns during a read query?

Native roles apply to whole tables or views, not single columns. You can build a separate view that excludes emails and phone numbers, or use a tool that rewrites matched fields in results.

The query runs. The emails stay hidden.