How to Configure Make Postgres Permissions

Published
Length
3 min read

Luis Felipe Dias

All posts

To set up make postgres permissions, create a dedicated database role with narrow table privileges. Then pass those role credentials to your Make automation scenario so it can run queries. Many teams skip this step when they build their first workflow. They reuse an admin account or the main app login to save time. That choice gives an automation tool full power to alter schemas or delete production rows. If a scenario has a bug, it can wipe out vital tables in seconds. A leaked key from the wo

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 make postgres permissions, create a dedicated database role with narrow table privileges. Then pass those role credentials to your Make automation scenario so it can run queries.

Many teams skip this step when they build their first workflow. They reuse an admin account or the main app login to save time. That choice gives an automation tool full power to alter schemas or delete production rows. If a scenario has a bug, it can wipe out vital tables in seconds. A leaked key from the workflow tool also opens the whole database to attackers. Setting up strict roles prevents these accidents before they happen.

How to set up make postgres permissions in your database

Start by creating a group role that holds the exact rights your workflows need. Postgres lets you set up group roles to manage privileges when you have many accounts. You then create a specific login user for Make and add it to that group.

Next, check what the special PUBLIC role allows inside your database. In Postgres, the PUBLIC role grants rights to every role on the system. By default, PUBLIC gets the right to connect to databases and create temporary tables. It also gets the right to run functions and procedures. The object owner can revoke these default rights so your workflow user starts clean.

You should also check the public schema rules on your server. In PostgreSQL 15 and later, regular users cannot create objects in the public schema by default. Older databases, or servers upgraded from older versions, might still allow this action. On those systems, an admin must revoke the create right on the public schema from PUBLIC.

After you lock down the defaults, grant only the exact rights the workflow needs. If a scenario only reads data, grant the select privilege on those target tables. Postgres lets you grant select on an entire table, a view, or a materialized view. You can even grant select on specific columns if a table holds private fields. Keep in mind that the select privilege also allows the copy to operation.

What native roles solve and what they leave open

Native database roles do a great job of limiting which tables a workflow can touch. They stop a read-only scenario from dropping tables or changing rows in other schemas. They also let you separate automation traffic from your main app accounts.

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 roles only check who logs in at the start of a session. They do not inspect what individual queries do while they run in flight. Once a role has select access on a column, it can read every row inside it by default. Native roles cannot rewrite matched fields like emails, phone numbers, card numbers, or national IDs. You also have to store long-lived database passwords inside your cloud automation platform. If you run dozens of workflows, rotating those stored passwords across every scenario takes hours.

Why query-level controls matter for workflow automation

Cloud workflows often pass database results straight to third-party apps, webhooks, or external APIs. A basic mistake in a scenario filter can pull thousands of customer records at once. When you rely only on table grants, the database sends all raw text to the workflow.

Adding runtime controls lets you filter data and track every statement without changing every role. You can enforce row limits, block risky commands, and mask sensitive columns before results leave. This keeps your automation fast while protecting the data inside your tables.

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

Can I limit Make to read only specific columns in Postgres?

Yes, Postgres lets you grant the select privilege on specific columns of a table or view. The workflow role will get an error if it queries any other column on that table.

Why can my new read-only role still run functions and create temp tables?

Postgres grants connect, temporary table creation, and function execution to the PUBLIC role by default. Every new role inherits PUBLIC rights until the object owner revokes them.

Does upgrading to PostgreSQL 15 remove public schema create rights?

New databases in PostgreSQL 15 block regular users from creating objects in the public schema. Upgraded databases keep their old settings until an admin revokes that right from PUBLIC.

The query runs. The emails stay hidden.