Multi-Tenant Query Scoping with Prisma Make every collection and item query operate inside the caller authorized dataset
Phase 19 - Authorization, Ownership, RBAC & Permissions Volume 05 - Authentication & Security
v
v
v
Phase 19 transforms verified identity into contextual, server-side authorization decisions.
Multi-tenant scoping must be automatic in every query A workspace SaaS app fails catastrophically if one collection endpoint forgets tenant filtering. TaskFlow therefore derives visible workspaces from current membership and scopes task queries accordingly.
request.user.id
v
v
v
v
Pagination, filtering, search, and sorting from Phase 15 operate inside the authorized dataset, not before it.
where: { project: { workspace: { memberships: { some: { userId: currentUser.id } }, }, }, // then Phase 15 filters: status, priority, search, etc. }
Order of reasoning • Establish identity.
• Map to application user.
• Constrain accessible resource set.
• Apply client filters within that set.
• Perform business operation.
Client context can improve UX, but the server still verifies membership and actual resource relationships on every request.
Prisma improves developer ergonomics, but migrations and generated queries still change a real relational database. You should be able to inspect both sides.
Restate the goal of “Multi Tenant Query Scoping with Prisma” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: domain intent → Prisma Client → generated SQL → PostgreSQL → mapped result. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Permission model + guards/policies protecting TaskFlow workspace/task actions with deliberate 401/403/404 semantics.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const tasks = await prisma.task.findMany({
where: { workspaceId },
orderBy: [{ createdAt: "desc" }, { id: "desc" }],
take: 20,
});Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Verify connection string, host, port, SSL/pooler mode, network reachability, and which environment file the process loaded.
Read the generated SQL before applying it and compare the change against existing production-shaped data.
Without copying the final source, create a second small scenario that applies “Multi Tenant Query Scoping with Prisma” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Map roles to capabilities without scattering role-name if statements across controllers.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.IDOR: trusting a resource ID without proving caller access
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.