How to Configure Make Supabase Read Only Access

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up make supabase read only access by creating a dedicated database user. Then you grant that user select rules on specific tables and schemas. Many teams take a shortcut and paste their default admin credentials into automation tools. If a workflow has a bug, broad permissions let it change or delete live data. Creating a separate read role stops automation tasks from writing to your database. How to set up make supabase read only access Every new project starts with a default postgre

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 read only access by creating a dedicated database user. Then you grant that user select rules on specific tables and schemas. Many teams take a shortcut and paste their default admin credentials into automation tools. If a workflow has a bug, broad permissions let it change or delete live data. Creating a separate read role stops automation tasks from writing to your database.

How to set up make supabase read only access

Every new project starts with a default postgres role that holds admin privileges. Your project does not give out full superuser access because that allows destructive actions. Instead, the default postgres role gets extra rights to manage the database. The password you set when creating the project belongs to this default admin role. Queries you run in the project dashboard also run as this default admin role.

You should never give this default admin password to a third-party service. Instead, Supabase recommends that you create a new database user for every outside service. To set up Make for reading data, you first create a dedicated role. You give this new role its own password and login rights.

Next, you grant usage on the target schema to this new role. Then you grant select permissions on the tables that Make needs to read. You can also set default privileges so the role can read future tables. Finally, you put the new role name and password into your Make database module. Now your automation workflows can read rows without being able to edit or drop them.

Why you should avoid default roles in Make

Each project also comes with built-in roles like anon, authenticated, and service_role. Teams sometimes use API keys tied to these roles inside their Make scenarios. Using a service role key in a simple read workflow creates a big risk. A small mistake in a scenario step could overwrite rows across your whole project. Even using the anon role can expose data if your table rules are too wide.

A dedicated Postgres user with select rights is much safer for automation tools. If someone leaks the Make credentials, an attacker still cannot change or delete records. If a developer builds a bad loop in Make, the database blocks any write statement. Separating users by service also helps you rotate one password without breaking other apps.

Auditor Read-Only Access + Customer Support Access to Production: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

What static read roles solve and what they miss

A dedicated read role solves the problem of accidental writes and deletes from Make. The database engine checks the role at login and blocks any update or drop query. It gives you a clear boundary between tools that read data and apps that write.

Still, a database role only decides who can log in and which tables they see. It does not check what individual queries do while they run in flight. A read role with select access on a customers table can still pull every column by default. That means Make workflows can pull raw emails, phone numbers, card numbers, or national IDs. Static roles also rely on long-lived passwords stored inside third-party automation tools. Also, basic role permissions do not give you per-query approval steps or field masking. Even when masking rewrites matched fields in results, static database roles cannot do that alone.

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 password in Make?

No, you should never share the default postgres password with an outside service. The default postgres role has admin privileges that allow major changes to your database. Always create a separate user with limited read rules specifically for Make.

How do I stop Make from writing to my tables?

Create a new database role and only grant it select rights on your tables. Do not grant insert, update, delete, or drop privileges to that user. When Make runs a write step, the database will reject the statement right away.

Can a read-only role still expose sensitive customer data to Make?

Yes, table-level select permissions let the user read every column in that table by default. If the table holds emails, phone numbers, or card numbers, Make will pull those values. You need column-level grants, database views, or data masking to hide sensitive fields.

The query runs. The emails stay hidden.