How to Configure Make Supabase Permissions

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up make supabase permissions by creating a dedicated database user for your workflow. Then you grant that user only the table privileges your automation needs to run. Many teams skip this step when they build their first automation. They paste the default project password into Make to get things moving fast. That default postgres role has admin privileges across the whole database. If a workflow goes wrong, it can delete tables or expose private rows. How make supabase permissions wor

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 supabase permissions by creating a dedicated database user for your workflow. Then you grant that user only the table privileges your automation needs to run.

Many teams skip this step when they build their first automation. They paste the default project password into Make to get things moving fast. That default postgres role has admin privileges across the whole database. If a workflow goes wrong, it can delete tables or expose private rows.

How make supabase permissions work in Postgres

Every Supabase project starts with a default postgres role and several built-in roles. The default postgres role acts as an admin, though it is not a full superuser. Supabase blocks full superuser status to stop destructive actions on the database. Even so, the password you set at project creation belongs to this admin role.

Supabase advises that you never give this admin password to an outside service. Instead, you should make a fresh database user for each tool you connect. When you run queries in the Supabase dashboard, they run as the postgres admin role. You can use the dashboard to create a role just for Make.

Once the new role exists, you grant it specific rights on specific tables. For example, a lead capture scenario only needs to insert rows into one table. It does not need to read customer billing data or drop schemas. You also need to decide how your scenario connects to the project. Some Make modules use the REST API, while others use a direct Postgres link.

When you use the API, built-in roles like anon come into play. When you use a direct database link, Postgres checks the grants on your custom user. Matching the right connection method with a tight role keeps your data safe.

Why native roles are only the first step

Creating a separate user for Make solves the biggest initial problem. It stops an automation tool from holding full admin keys to your project. If you stop using Make, you can drop that one user right away. Other services will keep working because they each have their own database users.

AI Agent Permissions + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Still, static database grants only check who logs in at the start. They do not inspect what individual queries do while they run in flight. A role with read rights on a customer table can pull every single row. It can also read sensitive columns like emails, phone numbers, and card numbers.

Static roles also leave gaps in how you track and approve changes. When Make runs ten workflows under one user, all queries look the same. You cannot tell which scenario or team member triggered a heavy update. You also cannot pause a risky delete query to ask a human for approval. Native roles set the boundary, but they do not govern live traffic.

Best practices for safer automation

Start by auditing every Make scenario that touches your database today. Replace any connection that still uses the default postgres admin password. Group your workflows by purpose and create separate database roles for each group. Give read-only roles to reporting workflows and write roles only where required.

Next, review which tables hold personal data like national IDs or phone numbers. Limit table grants so general workflows only touch the data they truly need. If a scenario only needs three columns, do not grant access to twenty. Rotate the passwords for your service roles on a regular schedule. Clear rules and small roles keep mistakes from turning into major outages.

Run guardrails and masking on the Postgres connection

Role grants and firewall rules are needed setup. Setup alone cannot check single SQL statements or mask sensitive rows in a response. By design, hoop.dev is an open-source proxy that sits beside Postgres, RDS, or Aurora as a sidecar for your Postgres. Clients and agent tools keep their credentials and point their connection string at the listener.

On each query, hoop.dev guardrails refuse disallowed drops, deletes, or table reads before they run. Next, hoop.dev data masking rewrites sensitive fields in returned rows that match your rules. Furthermore, hoop.dev holds SOC 2 Type II and logs every statement and verdict per resource. Check out the project on GitHub.

Frequently asked questions

Should I use the default postgres role for Make workflows?

No, the default postgres role has admin privileges across your database. Supabase recommends creating a separate user for every third-party service you use.

Does the Supabase postgres role have full superuser rights?

No, Supabase does not grant superuser access because it allows destructive actions. Instead, the default postgres role gets admin rights with extra privileges for safe tasks.

How can I protect sensitive columns from automation scenarios?

First, grant your Make database user rights only on the columns it needs. For deeper control, use data masking to rewrite emails or card numbers in results.

The query runs. The emails stay hidden.