How to Configure Make Snowflake Prevent Delete
To make snowflake prevent delete actions from Make workflows, create a dedicated service role. Grant that role only read, insert, and update permissions on your database tables. Teams often reuse broad admin roles when they set up Make modules. That habit gives every scenario the power to drop rows or wipe whole tables. How to make snowflake prevent delete with native roles Snowflake uses role-based permissions to control what a session can run. Every action on a database, schema, or table re
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.
To make snowflake prevent delete actions from Make workflows, create a dedicated service role. Grant that role only read, insert, and update permissions on your database tables. Teams often reuse broad admin roles when they set up Make modules. That habit gives every scenario the power to drop rows or wipe whole tables.
How to make snowflake prevent delete with native roles
Snowflake uses role-based permissions to control what a session can run. Every action on a database, schema, or table requires a clear privilege. When a Make scenario runs, it logs in using a set user and role. If that role holds delete privileges, any wrong module step can erase live records.
Start by creating a brand new role for your Make workflows. Give this role usage rights on the specific warehouse, database, and schema it needs. Next, grant select, insert, and update privileges on the exact tables the workflow touches. Leave out the delete and truncate privileges on every single table in that schema.
You should also check future grants on your active schemas. Future grants make sure new tables follow the same strict rules right away. Assign this restricted role as the default role for your Make service user. Do not link this service role to higher admin roles in your role tree.
Why native roles alone leave gaps
Native roles work well when every workflow needs the exact same table rules. They stop basic delete statements before the database engine can run them. They also keep your audit logs clean by tying actions to one service user. For simple data loads, a restricted role is the right first step.
Still, database roles have clear limits in complex daily work. A role is an all-or-nothing pass for the whole session. Sometimes a Make workflow must call a stored procedure that cleans up staging rows. If the procedure runs with caller rights, the role needs delete privileges to finish.
Once you grant delete for one task, every module using that role gets it. Native permissions cannot inspect the live query text or check how many rows match. They cannot tell a safe single-row cleanup from an unfiltered delete without a filter. They also cannot mask phone numbers or emails in query results on the fly.
Snowflake Access Control + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
How to harden Make workflow accounts
Split your Make workflows into separate service users based on what they do. Create one user and role for workflows that only read data for reports. Create a second user and role for workflows that insert or update customer records. Never share keys or passwords between these two accounts.
If a workflow must remove bad staging data, isolate that work in a separate schema. Grant delete permissions only on the staging schema, never on core production tables. Use stored procedures owned by a separate role to move clean rows into production. This pattern keeps destructive permissions away from the main Make session.
Review your query history logs each week to spot failed delete attempts. Failed commands show where a Make scenario tried to run an unsafe step. Fix the module logic in Make instead of expanding the database role permissions. Keep your role grants narrow so a broken automation never harms core business data.
Add runtime guardrails and masking beside your databases and APIs
Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits beside the service as an open-source proxy, a sidecar for your database or API.
Before a query runs, hoop.dev guardrails check the statement against your rules. An AI Analyzer you configure can score intent or hold risky calls for human review. Next, hoop.dev data masking rewrites sensitive fields in responses, and each verdict is logged per listener. Explore the MIT-licensed project on GitHub.
Frequently asked questions
Can I block truncate commands the same way I block delete commands?
Yes, truncate is a separate privilege or requires table ownership in the database. When you grant only select, insert, and update, the role cannot truncate tables.
What happens in Make when a module tries to run a blocked delete?
The database rejects the statement and returns a permission error to the Make scenario. Make then stops that module run and logs the error in your execution history.
Should my Make service user have a default role set?
Yes, setting the restricted role as the default ensures every session starts with safe permissions. Disable secondary roles for that user so it cannot combine privileges from other grants.
Related guides
In this post