How to Configure Snowflake Revoke permissions

Published
Length
3 min read

Luis Felipe Dias

All posts

You run a revoke statement on a role to apply snowflake revoke permissions. This action removes object rights from that role or pulls a role from a user. Most data teams group rights into job roles to speed up work. When roles grow too wide, users keep rights they do not need. A single mistake or bad query can then expose private tables. How snowflake revoke permissions work in your account Snowflake uses role-based rules to manage every database action in your account. You never give table r

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 run a revoke statement on a role to apply snowflake revoke permissions. This action removes object rights from that role or pulls a role from a user. Most data teams group rights into job roles to speed up work. When roles grow too wide, users keep rights they do not need. A single mistake or bad query can then expose private tables.

How snowflake revoke permissions work in your account

Snowflake uses role-based rules to manage every database action in your account. You never give table rights straight to a single user account. Instead, you grant rights to a role and assign that role to users. When you remove rights, you reverse this exact path in the system.

Only the object owner or a high admin role can remove a grant. If Role A grants a right to Role B, Role A can remove it. System admin roles can also step in to remove grants across the account. You must check which role granted the right before you try to pull it.

Roles often sit inside a parent and child tree structure. A parent role gets every right that belongs to its child roles. When you remove a right from a child role, the parent loses it too. If the parent still holds its own direct grant, it keeps that right.

Managed schemas change how grants and revokes work for your data team. In a managed schema, the schema owner controls all grants on inner objects. The table creator cannot give or pull rights on tables in that schema. This setup keeps grant rules in one central place for security teams.

How to handle dependent grants and future objects

Sometimes a role passes its own rights down to another role. This happens when the first grant includes the option to pass rights on. When you pull the base right, the system asks how to handle downstream grants. You can block the action if downstream grants exist, or you can cascade it.

A cascade action strips the right from every role down the chain at once. If you restrict the action, the system stops and warns you about dependent grants. Teams must check role chains before they run a cascade action in production. Breaking a role chain can stop scheduled jobs and reports without warning.

Snowflake Access Control + AI Agent Permissions: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Future grants add another layer of work for database admins. Teams often set rules that grant rights on all future tables in a schema. Pulling rights from current tables does not stop a future grant rule. You must remove the future grant rule itself to stop new table grants.

What native role revokes solve and what gaps remain

Native revoke rules clean up old rights and shrink bloated roles over time. They help teams pass audits and remove old users from sensitive schemas. Role cleanup is a vital base layer for any data security plan.

Still, native role rules only check who can log in and read a table. Once a user has select rights, they can run any read query they want. Native grants cannot check what an individual statement does while it runs. They cannot rewrite sensitive fields like emails, phone numbers, or card numbers on the fly.

Teams also struggle with standing rights that sit idle for months. Engineers often need temporary write rights to fix a broken table in production. If an admin forgets to run a revoke statement later, those wide rights keeps the session active. Manual role cleanup always lags behind real work and leaves data exposed.

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

Why does a user still have table rights after I pull them from a role?

The user likely holds a second role that also has rights on that table. Check all roles assigned to that user and check inherited parent roles too.

What happens to running queries when you pull a role from a user?

Active sessions may need to switch roles or end before every change takes full effect. Pulling object rights from a role blocks new queries on that object right away.

Do I need to pull future grants and current grants in separate steps?

Yes, removing a future grant rule only stops rights on new objects created later. You must also pull rights on existing tables to remove current permissions.

The query runs. The emails stay hidden.