How to Configure Make Snowflake Permissions
You set up make snowflake permissions by creating a custom role with narrow grants. Then you bind that role to a service user for your automation scenarios. Many teams skip this step and use a shared admin role instead. Broad roles let automated workflows read or change every table in the warehouse. One bad scenario update can wipe out records or leak private data. How make snowflake permissions work in practice Snowflake uses role-based rules to control what a user or tool can do. Nothing is
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 snowflake permissions by creating a custom role with narrow grants. Then you bind that role to a service user for your automation scenarios. Many teams skip this step and use a shared admin role instead. Broad roles let automated workflows read or change every table in the warehouse. One bad scenario update can wipe out records or leak private data.
How make snowflake permissions work in practice
Snowflake uses role-based rules to control what a user or tool can do. Nothing is allowed by default until an admin grants rights to a role. You must grant usage on the warehouse, the database, and the schema first. After that, you grant select, insert, or update rights on specific tables.
Make runs cloud workflows that send queries to your data warehouse on a schedule. To do this, the automation app logs in as a specific warehouse user. That user has a default role assigned to its profile in the warehouse. Every module in your scenario inherits the exact rights of that default role.
Good setup means creating a dedicated role just for your automation tool. You should never attach system admin or account admin roles to workflow users. Instead, build a custom role that touches only the staging tables Make needs. If a scenario only adds new leads, grant insert rights on that one table. Do not grant read rights on customer billing tables if the workflow does not need them.
What native roles solve and what they miss
Native roles are great at deciding who can log in and see objects. They stop a marketing workflow from touching finance schemas or dropping production databases. They also let you separate compute warehouses so background tasks do not slow down reports. When you set up narrow roles, you shrink the blast radius of a leaked key.
Still, static warehouse roles only check permissions at the object level before a query runs. Once a role has select rights on a table, it can read every row by default. It can also pull sensitive columns like emails, phone numbers, and card numbers. Native roles cannot pause a risky delete statement from a broken scenario in flight. They also cannot require a human to approve a sudden bulk export from Make.
Snowflake Access Control + AI Agent Permissions: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
How to keep automated warehouse workflows safe
Start by giving each major business workflow its own user and custom role. A sales sync and a support sync should not share the same login credentials. This split makes it easy to read query logs and spot broken scenarios fast. If one integration fails or misbehaves, you can revoke its role without stopping other teams.
Next, review the query history for your service roles at least once a month. Look for tables the role has permissions to use but never queries in real runs. Drop those extra grants right away so the role stays small and focused. Also rotate the keys or tokens stored in your Make scenarios on a regular schedule. Finally, use column masking policies so queries rewrite emails and national IDs in results.
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
What minimum grants does a Make scenario need in Snowflake?
The custom role needs usage on the warehouse, database, and schema it will use. It also needs specific table rights like select or insert for its exact task.
Should different Make scenarios share the same warehouse role?
No, sharing one role across many workflows gives every scenario too much power. Create separate roles for different teams so each workflow only touches its own tables.
How do you protect sensitive columns from automation workflows?
Restrict the role to safe views or apply masking policies to the base tables. Masking rewrites matched fields like phone numbers and card numbers in query results.
Related guides
In this post