REVOKE removes previously granted privileges from a BigQuery user, group, or service account.
REVOKE removes one or more privileges from a principal on a dataset, table, or view, immediately stopping that principal from performing the associated actions.
Use the REVOKE statement followed by the privilege list, ON object, FROM principal.You can target individual tables or an entire dataset.
Run REVOKE SELECT ON `project.dataset.Products` FROM "user:alice@example.com"; to block Alice from reading the Products table.
List each privilege separated by commas.Example: REVOKE SELECT, INSERT, UPDATE, DELETE ON `project.dataset.Orders` FROM "group:analysts@example.com";
BigQuery ignores the REVOKE with no error, making the command safe to run in automation scripts.
Yes, replace the table name with the dataset: REVOKE ALL ON SCHEMA `project.dataset` FROM "serviceAccount:app@project.iam.gserviceaccount.com";
SELECT * FROM `region-us`.INFORMATION_SCHEMA.TABLE_PRIVILEGES WHERE grantee="user:alice@example.com"; shows existing rights so you know exactly what to revoke.
Grant and revoke access on Google Groups to simplify management and reduce accidental exposure.
Your account must hold bigquery.datasets.update on the dataset or bigquery.tables.updateData on the table.Ask an admin to grant temporary authority.
1. Identify principal → 2. Verify current rights → 3. REVOKE privilege ON object FROM principal → 4. Test access.
.
No. REVOKE only affects dataset, table, or view privileges, not IAM roles. Use gcloud projects remove-iam-policy-binding instead.
Yes. If a user loses SELECT on a base table, any view referencing that table also becomes inaccessible.
Yes. Simply GRANT the same privileges back to the principal.