Preparing the next view without exposing private workflow data.
Database engineering · Phased project
Enforce organization boundaries in a relational case schema
A fictional case-management application filters most requests correctly, but imports and background commands can connect a case to another organization's project or assignee.
Practice brief · Version 5
Project scope
10 tickets / 3 phases
Total focused work estimate
30h 15m + setup
Suggested stack
PostgreSQL · Prisma · TypeScript
Recommended next step
Start with ATENANT-101
Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
Practice tenant-aware keys, foreign keys and direct-write denial tests.
What the team gains
Review defense in depth for data isolation across ordinary and privileged writers.
Before you start
Create two synthetic organizations with overlapping display names.
Use repository-level authorization and migration-backed constraints.
Delivery agreement
Ten scoped tickets across three phases. Build a synthetic local service or select a ticket after recreating its prerequisites; estimates exclude setup.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.