Open-source Firebase alternative with PostgreSQL, auth, and real-time

How to Record Supabase

Record Supabase Dashboard on demo projects, not production. Guide for RLS tutorials, schema design, and auth configuration recordings.

When you’d need to record Supabase

Supabase setup tutorials for beginners

Record the full Supabase setup — create project, create tables, set up RLS policies, configure authentication. Supabase's UI is developer-friendly but first-time setup still needs visual guidance.

Row Level Security (RLS) configuration

Record RLS policy creation — enable RLS on a table, write policies for SELECT/INSERT/UPDATE/DELETE, test with different user roles. RLS is Supabase's most confusing feature and the #1 source of support questions.

Database schema design walkthroughs

Record table creation, foreign keys, indexes, and database functions using Supabase's Table Editor and SQL Editor. Show both the visual editor and the generated SQL.

Auth configuration demonstrations

Record auth provider setup — enable Google/GitHub OAuth, configure email templates, set up redirect URLs. Show the Settings > Authentication page and test the sign-in flow.

Recommended settings

Resolution

1920x1080

Frame rate

30fps

Audio

Microphone only

Capture mode

Window Capture

Things to know

•Supabase Dashboard shows project URL and anon/service_role keys on the Settings page — these are API credentials
•Table Editor shows actual row data — user records, auth data, and application state
•The SQL Editor saves query history — previous queries may reference sensitive data or infrastructure
•Auth section shows user email addresses, UIDs, and authentication providers

Step-by-step

1
In Screenify Studio, select Window Capture and pick the Supabase window.
Use a demo Supabase project. Settings > API shows project URL and API keys — avoid navigating to this page unless you blur the keys.
2
Open Supabase Dashboard. Use a demo project, not production — the Table Editor shows real data, Auth shows real user emails, and Settings shows API credentials.
3
Navigate to the section you'll record (Table Editor, SQL Editor, Auth, Storage). Supabase's sidebar has many sections — go to the right one before starting.
4
If showing the Table Editor, check visible row data. User tables, auth.users, and any table with PII should use demo data or a fresh project with seed data.
5
When showing the SQL Editor, check your query history (sidebar). Previous queries like 'DELETE FROM users WHERE email = ...' or 'SELECT * FROM payments' are visible.

Pro tips

Auto-zoom on RLS policies. Supabase's RLS policy editor shows the SQL policy condition in a compact text area. When you write `auth.uid() = user_id` as a policy condition, auto-zoom makes the SQL readable — crucial because RLS policies are the exact content viewers are trying to learn.

Use a fresh project with seed data. Supabase projects are free to create. Start a new project, run your migration SQL to create tables, seed with test data. Your production project's auth.users table has real customer emails. A 5-minute setup avoids the risk entirely.

Show the SQL alongside the visual editor. When creating a table in the Table Editor, click 'Show SQL' to reveal the generated CREATE TABLE statement. Showing both teaches viewers the visual interface AND the SQL underneath — valuable for developers who'll eventually write SQL directly.

Demonstrate RLS with the API. After setting RLS policies, test them by making API calls (from the client or the SQL Editor as a specific user). Don't just write the policy — prove it works by showing an allowed request succeed and a denied request fail.

Common mistakes

Recording on a production project. Table Editor shows real user data. Auth shows real email addresses. Settings > API shows your production API keys and project URL. Everything in a production Supabase project is sensitive. Use a demo project.

Navigating to Settings > API on camera. This page shows your project URL (`https://xxx.supabase.co`), anon key, and service_role key in plain text. The anon key is designed to be public, but the service_role key bypasses RLS. Don't show this page unless you blur the keys.

Teaching tables without teaching RLS. You show how to create tables and insert data but skip RLS. Viewers deploy with RLS disabled and their database is publicly readable. Always demonstrate RLS as part of any table creation tutorial.

Showing SQL Editor history with sensitive queries. Your SQL Editor sidebar shows saved and recent queries: 'UPDATE users SET role = admin WHERE email = ceo@company.com'. Review and clear history before recording.