It would be extremely helpful if Supabase introduced a dedicated Billing role within the Team Member permissions system—one that allows a user to manage billing settings, payment methods, and invoices, but does not grant access to project data or administrative controls.
Right now, Supabase team roles are fairly coarse‑grained. If an organization wants to give someone access to billing (e.g., a finance team member or accountant), they must grant a broader role than necessary. This creates two issues:
Many SaaS platforms solve this by offering a dedicated billing‑only role.
Vercel provides a Billing role that allows a user to:
…without granting access to deployments, environment variables, project settings, or team configuration.
This separation of duties is extremely useful for teams of all sizes.
Add a new Billing role to the Supabase Team Member roles list with permissions limited to:
And explicitly no access to:
This would be especially valuable for companies using Supabase in production environments where billing access must be isolated from technical access.
Hichem Fantar requests a dedicated 'Billing' role within Supabase's team member permissions. This role would allow users to manage billing settings without access to project data or administrative controls, addressing security and operational concerns. The request aligns with practices seen in other SaaS platforms like Vercel.
@clicktodev This is a common enterprise request ("Finance Role"). Currently, the workaround is to invite them as a minimal user but they still see too much. Strong +1 for a dedicated billing scope. In the meantime, many teams create a dedicated "billing@company" account that owns the org, so finance logs in with that, and devs have their own accounts.