Lock Supabase Studio Table Editor #12432
Replies: 5 comments
-
Great suggestion and one we think could be possible to implement with user roles down the road. I'm going to note it in our internal backlog as something to consider down the road. Appreciate the feedback! |
Beta Was this translation helpful? Give feedback.
-
This is a part duplicate of https://github.com/orgs/supabase/discussions/16759, but we'll keep both open since they both have 1 upvote and cover different use cases. |
Beta Was this translation helpful? Give feedback.
-
Any updates on this? Would love to be able to lock my tables in prod from being edited in the dashboard |
Beta Was this translation helpful? Give feedback.
-
Any update on this @saltcod? I have experienced major pain resolving divergence between our db and migrations files because a collaborator on the team inadvertently made several changes on the dashboard |
Beta Was this translation helpful? Give feedback.
-
+1 on this issue, this is a major security hole in production! |
Beta Was this translation helpful? Give feedback.
-
Feature request
Add a setting to prevent any edits to the schema via the table editor in Supabase Studio
Is your feature request related to a problem? Please describe.
If you're developing Supabase locally and are creating migrations to change the "production" environment (via
supabase db push
), things can get really messed up if someone happens to edit the schema via the table editor. This is exacerbated by the fact that Supabase Studio looks pretty similar betweenapp.supabase.io
andlocalhost
, so one could accidentally modify things thinking it's the local editor.Describe the solution you'd like
I would think a boolean setting preventing changes to the Table Editor would suffice. v2 could be "admins only" or something.
Beta Was this translation helpful? Give feedback.
All reactions