Row Level Security: a bouncer for every table
Understand Row Level Security, write the rules by prompt so that anyone can read the menu and place an order but nobody can read the orders, and prove each rule works yourself with the 3-question check.
Why this matters
This is the most important lesson in the course. Not the most exciting, the most important.
Here's why. In Lesson 7.5, your website will talk to Supabase using a publishable key, and that key will be inside the browser code that every visitor downloads (Lesson 6.4: anything public is public). So anyone, anywhere, can take that key and send their own requests to Adjoa's database. That's normal: it's how Supabase is designed. The only thing standing between a stranger and every customer's phone number is the set of rules you write today.
Getting this wrong is how real apps leak real customers' data. And the AI won't always save you: when an error says "permission denied", the quickest "fix" an AI can offer is to switch the rules off. That's why this course doesn't let the AI have the final word on security. Cursor writes the rules. You check them with three questions, and you prove them by trying to break in.
If this feels serious, good. It is. It's also very doable: two tables, four rules, three questions.
In the full lesson
- The idea in plain English
- Do it
- The prompt
- Check it worked
- Understand what AI wrote
- Quick check
- What you can do now
The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.