Topic
Data and access
Who can see what, and where that rule is enforced. These pieces are about moving an access rule below the application code — into the database itself — so a new screen or a new client cannot leak another client's data just by someone forgetting to add a check.
-
Sep 5, 2026 Note For AI-coders
Why I put the authorization rule in the database, not the app
Multi-tenant ticketing with row-level security, and why "you can only see your own company's tickets" belongs below the application code.
-
Sep 5, 2026 Note For both
Where the rule lives
"You can only see your own company's tickets" is one sentence. Where a team chooses to enforce it decides whether the next feature can forget it. A story about moving a rule below the code, told for people who will never write a database policy.
-
Sep 5, 2026 Build For both
A client portal where every client sees only their own work
A ticketing system with a client portal and tenant isolation enforced in the database itself.