How to Configure Make Supabase Prevent Delete

Published
Length
3 min read

Luis Felipe Dias

All posts

To make supabase prevent delete in automated workflows, create a dedicated database user without delete permissions. You then use that restricted role in your Make scenario instead of the admin account. Many teams start by pasting their default admin password into third-party automation tools. This shortcut gives external workflows full power to drop tables or erase customer rows. A single bad trigger or logic bug in a scenario can wipe out production data. How to make supabase prevent delete

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 supabase prevent delete in automated workflows, create a dedicated database user without delete permissions. You then use that restricted role in your Make scenario instead of the admin account. Many teams start by pasting their default admin password into third-party automation tools. This shortcut gives external workflows full power to drop tables or erase customer rows. A single bad trigger or logic bug in a scenario can wipe out production data.

How to make supabase prevent delete with database roles

Every new project comes with a default postgres role that holds admin privileges. Supabase withholds true superuser status to block destructive system commands, yet this role remains very powerful. Queries that you run inside the project dashboard execute under this default admin role. The docs warns teams not to share the default project password with external services. Instead, you should create a fresh database user for each external service you link.

This role separation is the foundation for safe automation with Make. When you build a Make scenario, it needs a database user to run queries. If you hand Make the default admin login, every module in your workflow can delete rows. To stop deletions, you create a custom role dedicated to your Make integration. You grant this new role select, insert, and update privileges on specific tables only. You leave out the delete privilege and table drop rights.

Row level security policies offer a second layer of protection when workflows use project APIs. Database rules can check the active role before allowing any change to a table. If a workflow only needs to add new leads or update order statuses, it does not need delete rights. By withholding the delete grant at the database level, Postgres rejects any removal request from Make.

Why static database roles leave operational gaps

Native database roles and table grants solve the basic problem of overly broad service accounts. They let you draw a clear line around which tables an external tool can touch. Creating a separate user for Make also makes it easier to rotate credentials later. If a scenario stops running, you can revoke that single user without breaking other apps.

Still, static roles only decide who can log in and which broad command types they can run. A role permission check cannot inspect the actual intent or volume of an individual query in flight. For example, a role with update permissions can still overwrite every row in a table with blank values by default. From a business view, setting an email column or phone number to null is just like deleting it. Static grants also apply the exact same rules at all times for that user.

End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Teams often struggle to maintain dozens of custom roles as their Make scenarios grow. When a developer needs to run a one-time cleanup task, they might grant delete rights temporarily. Those temporary permissions often stay active forever because nobody remembers to revoke them. Native role setups also lack field-level data masking for sensitive results returned to third-party tools. If a workflow reads a customer table, the database returns raw emails, phone numbers, and card numbers.

Managing human and automated database queries safely

Relying only on static database users forces a hard choice between safety and speed. If you lock down roles too tightly, builders get blocked and share the default admin password again. If you keep roles too open, a runaway Make scenario or human mistake can ruin production tables. Teams need a way to inspect individual statements and require approval for risky actions before they run.

Add query and result controls beside Postgres

Grants and pools govern who logs into PostgreSQL. Yet every query in an open session still runs with that role's full scope. In practice, hoop.dev runs beside your database as a sidecar for your Postgres. It reads plain and prepared queries on the wire with no change to your users or drivers.

When a tool or agent sends SQL, hoop.dev Postgres controls check each statement against your deny rules. An AI Analyzer you configure can also score intent or hold a risky query for human review. Matched sensitive columns in result rows are masked in memory before they reach the caller. Each query and decision is logged per listener, which generates evidence for SOC 2, HIPAA, and GDPR audits. View the binary on GitHub.

Frequently asked questions

Why should I not use the default postgres role in Make?

The default postgres role has admin privileges across your database. Sharing its password lets a faulty Make scenario delete rows or change tables without limits.

Does Supabase give superuser rights to the default role?

No, Supabase does not grant superuser status because it allows destructive system operations. Instead, the default postgres role gets admin privileges with specific extra permissions.

How do I stop Make from deleting rows while allowing updates?

Create a dedicated Postgres user just for your Make workflows. Grant that user select, insert, and update rights on your target tables, and omit the delete grant.

The query runs. The emails stay hidden.