https://supabase.com/docs/guides/platform/shared-responsibil...
You are responsible for a workflow that's suitable for your application. Once you get into production, you should be using Migrations for every database change. I have a more thorough response here: https://news.ycombinator.com/item?id=36006018
You should make the default editor read only and allow switching to write mode with a big warning. This would discourage people from writing SQL or using UI to modify in production.
The dashboard has always screamed "use me to edit" and I have used supabase in the beginning and very recently too. Nothing has changed to discourage it so far.
Maybe something like mode button which is present at top and you can click to switch between development and production mode?
This would also change a couple more things which you do not want to touch in production by accident.
If anything, I think the admin dashboard encouraging directly doing operations on the database is the biggest weakness of Supabase. I would much prefer being able to lock it down to purely CI-driven migrations.
[1]: https://supabase.com/docs/guides/getting-started/local-devel...