How to Configure BigQuery Create User

Published
Length
3 min read

Luis Felipe Dias

All posts

You cannot run a standard SQL statement for a bigquery create user workflow. Instead, you grant Google Cloud IAM roles to an existing email or service account. Most data teams start by assigning project-wide roles to help analysts move fast. Still, broad roles let users read private tables and run costly queries across every dataset. How the bigquery create user process works in Google Cloud Traditional databases keep their own list of local user accounts and passwords. Google Cloud works in

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 cannot run a standard SQL statement for a bigquery create user workflow. Instead, you grant Google Cloud IAM roles to an existing email or service account. Most data teams start by assigning project-wide roles to help analysts move fast. Still, broad roles let users read private tables and run costly queries across every dataset.

How the bigquery create user process works in Google Cloud

Traditional databases keep their own list of local user accounts and passwords. Google Cloud works in a different way. It manages every identity through a central cloud directory before any query runs. To completes a bigquery create user request, an admin picks a Google account first. This account can belong to a human engineer, a team group, or a software app.

Next, the admin attaches specific roles to that identity at the project or dataset level. One role lets the user run jobs and consume compute power inside the project. Another role lets the user read table data or write new rows into a dataset. A user needs both job permissions and data permissions to run a basic query.

Teams should assign roles to groups rather than single people whenever possible. When a new analyst joins the team, you add their email to the group. They get the right dataset permissions right away without extra setup work. When they leave the team, you remove them from the group to revoke access.

Choosing between human accounts and service accounts

You will manage two main account types when you set up warehouse permissions. Human users log in with their work emails to run ad-hoc queries and explore tables. Service accounts exist for automated pipelines, reporting dashboards, and backend apps. Both account types use the same role system to read and write data.

Many teams make the mistake of sharing one service account key across many engineers. When five people use the same key, your audit logs break down. You can see that a bad query ran, but you cannot see who wrote it. Worse, someone might paste that static key into a script or a chat room. Give every human their own account, and keep service accounts strictly for automated code.

User Provisioning (SCIM) + BigQuery IAM: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Why native roles leave a gap during live queries

Cloud roles do a great job of deciding who can enter the data warehouse. They block unknown users and restrict which datasets a team can view. Still, static roles only check permissions at the front door. Once a user has read rights on a table, they can pull every single row.

This all-or-nothing access creates two big risks for growing engineering teams. First, an analyst debugging a billing issue might pull raw customer emails or card numbers. Static table roles cannot rewrite sensitive fields on the fly based on who is asking. If you build separate masked views for every team, you double your storage management work.

Second, permanent roles stay active twenty-four hours a day, seven days a week. An engineer who needs prod write access for ten minutes keeps that power all year. If a bad script runs under their account, it can drop tables before anyone notices. Native cloud roles do not pause risky statements and ask a peer for approval.

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 sits inline in the protocol beside each supported service as an open-source proxy, a sidecar for your database or API. For every query or command an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human approval.

First, hoop.dev guardrails block banned queries before they run or hold risky ones for review, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.

Frequently asked questions

Can I add a user in BigQuery with a SQL command?

No, the warehouse does not support standard SQL commands that create local database users. You must create identities in Google Cloud IAM and grant them roles on your datasets.

What happens if I only grant data viewer permissions to a new user?

The user will see the dataset and table names, but their queries will fail. They also need a job user role at the project level to run compute tasks.

How can I protect sensitive columns when granting read access?

You can set up policy tags on specific columns or add runtime data masking. Data masking rewrites matched fields like phone numbers or national IDs in the query results.

The query runs. The emails stay hidden.