Database review
Review Adjoa's database like a security auditor: run Supabase's Security Advisor, list every table, grant and policy, take each table through the 3-question check, confirm the database's own checks guard the side door, and grow the stranger test from three tests to seven.
Why this matters
In Lesson 10.1 you scored "open database" as one of the worst things that could happen to Adjoa: every customer's name, phone number and email, readable by anyone. You built the defences in Modules 7 and 9. But since then you've added a column, opened two doors for the owner, and asked Cursor to change things many times. Every change is a chance for a rule to drift.
A review is how professionals catch drift. You don't rebuild anything. You list what's really there, compare it with what should be there, and prove the important parts again. You'll also get a second opinion from Supabase itself: its Security Advisor checks your project for the mistakes it sees most often across thousands of apps.
This lesson changes almost nothing. If it does find something, you'll be very glad you looked.
In the full lesson
- The idea in plain English
- Do it
- 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.