How to Configure Make Neon Permissions
You set up make neon permissions by creating a custom database role in Neon. Then you add those role credentials to your Make workflow steps. Many teams skip this step and use the default project owner account instead. Using an owner role gives every automated scenario full control over your tables. One bad step in a workflow can drop tables or expose private records. How make neon permissions work in practice Neon runs on Postgres and uses standard database roles to control data rules. When
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 neon permissions by creating a custom database role in Neon. Then you add those role credentials to your Make workflow steps. Many teams skip this step and use the default project owner account instead. Using an owner role gives every automated scenario full control over your tables. One bad step in a workflow can drop tables or expose private records.
How make neon permissions work in practice
Neon runs on Postgres and uses standard database roles to control data rules. When you create a project, the platform gives you a powerful default role. To lock down your workflows, you must create a separate role with fewer rights. You can limit this new role to specific schemas, tables, or actions. For example, a reporting workflow only needs permission to read rows from selected tables. An ingestion workflow might only need permission to insert new records into one table.
After you set up the role in Neon, you move to Make. Make connects to your database using standard Postgres credentials stored in a module. You paste the host, database name, user, and password into the module settings. Make then uses that single role for every task tied to that credential. Every time a webhook triggers the scenario, Make logs in as that database user. The database checks the role permissions before it lets the query run.
Where native database roles fall short for automation
Database roles are great at deciding which user account can log in. They also control which tables that account can read or change at rest. Still, native roles cannot inspect individual queries while they run in flight. Once a role has read access to a table, it reads every column by default. If that table holds emails, phone numbers, or card numbers, Make pulls them all.
This creates a big risk when workflows pass database outputs to outside tools. A scenario might send customer rows to an external chat app or email tool. Native roles also lack a way to require human approval for risky updates. If a workflow has permission to delete rows, it runs the delete right away. Plus, shared automation credentials make audit logs hard to read during a review. Every query from Make looks identical in the database log, hiding which scenario ran.
AI Agent Permissions + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Best practices for safer workflow database setups
Start by creating one dedicated database role for each major Make scenario. Never share the default project owner password with an outside automation platform. Grant each role access to the exact tables and columns it needs today. If a workflow only reads data, do not give it write or delete rights.
You should also separate your test workflows from your live production database branches. Neon lets you create isolated branches so you can test scenarios without risk. Rotate the passwords stored in Make on a regular schedule to limit key leaks. Finally, review your active Make connections every quarter and remove old database roles.
Check every Postgres query on the wire
Database roles and network rules decide who can open a session. They do not read what each SQL statement does after login. With hoop.dev, you run an open-source proxy, a sidecar for your Postgres. It runs beside your database and reads the Postgres wire protocol. Your apps and agents keep their login details and change only the host and port in the connection string their tool uses.
Before a query runs, hoop.dev guardrails check the statement by its effect, table, or pattern. They refuse bad deletes or drops with a real Postgres error. On the way back, hoop.dev data masking rewrites sensitive values in returned rows based on your rules. Every query and verdict goes to the audit trail. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and generates evidence for HIPAA, GDPR, and PCI DSS. See the code on GitHub.
Frequently asked questions
Should Make workflows use the default Neon database owner role?
No, the default owner role can drop tables and read all sensitive records. Always create a separate role with limited table rights for your Make modules.
Can database roles stop Make from pulling sensitive columns like emails?
Standard table grants allow access to the whole table at once. You must set up column rules or use data masking to rewrite emails and phone numbers.
How do we track which Make scenario ran a specific database query?
Give each high-impact scenario its own database user role in Neon. This ensures the database log shows a distinct username for each workflow run.
Related guides
In this post