How to Configure Make Supabase Sandbox

Published
Length
3 min read

Luis Felipe Dias

All posts

To set up a make supabase sandbox, create a dedicated database user for your Make workflows. Then link Make to your test project using that scoped role instead of the main admin password. Many teams take a shortcut and paste the default project password into their automation tools. That habit gives every workflow full admin rights over the test database. If a test scenario has a bug, it can wipe tables or expose test records across the whole project. How to set up a make supabase sandbox with

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 set up a make supabase sandbox, create a dedicated database user for your Make workflows. Then link Make to your test project using that scoped role instead of the main admin password. Many teams take a shortcut and paste the default project password into their automation tools. That habit gives every workflow full admin rights over the test database. If a test scenario has a bug, it can wipe tables or expose test records across the whole project.

How to set up a make supabase sandbox with safe roles

Every Supabase project starts with a default postgres role. This role has admin privileges across the database. Supabase does not grant true superuser access because superusers can run destructive system commands. Still, the default postgres role still holds broad admin power. The password you pick at project creation belongs to this role. Supabase advises teams never to share this password with an outside service. Instead, you should create a new database user for each external tool.

When you build a make supabase sandbox, start by making a dedicated role just for Make. Give this role permission to read or write only the specific tables your scenario needs. Supabase also includes built-in roles like anon, authenticated, and service_role for API requests. If your Make scenario connects through the API instead of a direct database link, avoid using the admin key when a basic role works. Queries run inside the Supabase dashboard execute as the default postgres role and carry a dashboard source comment. Keeping Make on its own user separates automation traffic from human dashboard queries.

Why native roles are not enough for automation

Creating a separate user for Make solves the first problem of shared admin passwords. You know which service logged in, and you limit which tables it can touch. Still, database roles only check who logs in at the start of a session. They do not inspect what individual queries do while they run.

Suppose your Make scenario needs to read customer rows and update order status in the sandbox. Once the role has read and write access to those tables, a broken loop in Make can still delete rows or dump thousands of records. Also, test databases often hold copies of real emails, phone numbers, card numbers, or national IDs. Standard database permissions return those raw values to every valid query. Static credentials stored inside Make also stay active until someone rotates them by hand. If a team member leaves or a scenario gets shared, that password stays valid.

AI Sandbox Environments + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Keeping sandbox data and queries under control

To run automation safely, teams need controls that work on every query in flight. First, test workflows should not hold long-lived database passwords. Second, you need a way to block dangerous statements like table drops or mass updates before they hit the database, even if the role allows table writes. Third, data masking should rewrite matched fields like emails, phone numbers, and card numbers in query results. That way, Make scenarios process realistic payloads without storing sensitive values in automation logs. Finally, every query from Make should leave a clear audit trail tied to the exact workflow and user.

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

Should I use the default postgres password in my Make sandbox?

No. The default postgres password grants admin rights across your project. Supabase recommends creating a separate database user for every third-party service so you can limit and revoke its access easily.

How do dashboard queries differ from Make queries in Supabase?

Queries you run in the Supabase dashboard execute under the default postgres admin role and include a dashboard source comment. Make queries should run under a custom role with limited table permissions.

How can I protect sensitive data in a Supabase sandbox used by Make?

Scope the database user to specific tables and apply data masking to rewrite emails, phone numbers, card numbers, and national IDs in results before Make logs the response.

The query runs. The emails stay hidden.