How to Configure Supabase Create User
To run a supabase create user workflow, you add a new database role through the admin account. You then grant that role only the table rights it needs for its job. Many teams skip this step and share the main project password across several services. That shortcut gives every app and engineer broad admin rights over your whole database. If one service fails or leaks its key, all your tables face risk. How the supabase create user process works Every new project comes with a default admin role
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 run a supabase create user workflow, you add a new database role through the admin account. You then grant that role only the table rights it needs for its job. Many teams skip this step and share the main project password across several services. That shortcut gives every app and engineer broad admin rights over your whole database. If one service fails or leaks its key, all your tables face risk.
How the supabase create user process works
Every new project comes with a default admin role named postgres. This default role holds admin rights, not full superuser power. The platform blocks superuser rights to stop bad commands from breaking the underlying system. Even so, the default admin role can create new users and grant table rights. When you set up a project, you pick the password for this admin role.
You should never share that main admin password with outside tools or extra apps. Instead, the vendor says you should make a fresh database user for each service. You can run this setup from the web dashboard. Every query you run in the dashboard runs as the default admin role. These dashboard queries also carry a text note showing they came from the dashboard.
Each new project also includes built-in roles for app traffic, such as anon. While built-in roles handle normal app requests, custom database users serve direct database tasks. An engineer or a reporting tool might need a direct login to read tables. When you make a new user, you prevent them from using the main admin login. You also stop them from attempting superuser changes, which the platform rejects anyway.
Why you should split roles by service
Giving each service and team member a distinct database user limits damage during an incident. When ten tools share the default admin login, you cannot tell which tool ran a bad query. Every query looks the same in your logs because they all use the same role name. If you need to rotate the password, all ten tools break at the same time.
Separate users fix this problem at the login step. You can grant read rights on one schema to a reporting tool. You can give write rights on one table to a worker script. If the reporting tool gets compromised, you just drop or lock that single user. Your other services keep running without any downtime or password changes.
User Provisioning (SCIM) + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native database roles solve and what they miss
Native database roles do a great job of checking who can log in. They also define which tables and schemas a user can read or change. Once a user logs in, the database checks their role before running a query. This setup stops a read-only user from dropping a table or changing rows.
Still, static database roles only check permissions at the table or schema level. They do not inspect what individual queries do while they run in flight. A user with read rights on a customer table can still pull every row at once by default. Native roles alone do not rewrite sensitive fields like emails, phone numbers, or card numbers in results. They also require you to manage and rotate static passwords for every single user you create. When engineers need temporary write rights for a fix, someone must grant and revoke roles by hand. Teams often forget to revoke those extra rights after the fix is done.
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 sits inline in the Postgres protocol beside Postgres, RDS, or Aurora as a sidecar for your Postgres. On every production query from an engineer or AI agent, hoop.dev decides whether to pass, mask, block, or hold it for approval.
First, hoop.dev guardrails refuse disallowed drops or deletes before they run, and risky statements can pause for human review. Next, hoop.dev data masking rewrites sensitive fields in returned rows in memory. 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
Does the default admin role have full superuser rights?
No, the default postgres role has admin rights, not full superuser power. The platform blocks superuser access to prevent destructive actions on the database.
Should I give the main project password to third-party services?
No, you should keep the main admin password private unless you fully trust the service. The vendor recommends making a separate user for every external service you use.
What role runs queries inside the web dashboard?
Queries that you run inside the web dashboard execute under the default postgres admin role. The system also adds a comment to those queries showing they came from the dashboard.
Related guides
In this post