CASE STUDY 01 / FIELD OPERATIONS
A business operations project connecting dispatch, technician work, time, parts, and invoicing. Its security story starts with a simple rule: one organization’s work must stay inside that organization.
01 / SYSTEM VIEW
A simplified view to support a technical conversation.
Dispatch, work orders, and business records
Assignments, time, parts, and closeout
Role permissions · organization context · validated inputs
Prisma / PostgreSQL records
Worker and queued jobs
Conceptual architecture based on the project summary. Organization context must remain attached to work that crosses into background processing.
02 / ENGINEERING DECISIONS
Implementation choices paired with the tradeoffs they introduce.
The repository’s isolation tests exercise both API requests and the tenant database client. This checks the boundary below individual screens.
A scoped client helps reduce repetition, but every new query path and relation still needs review.
A work order must not link to another organization’s site, technician, or customer simply because the submitted ID is valid.
Checking the primary record alone leaves related records as a separate authorization surface.
The selected test file also checks that audit entries stay inside their organization.
Operational visibility is useful only when logs and history respect the same privacy boundary as business data.
03 / REVIEW SCENARIOS
Illustrative explanations of selected test definitions. These controls do not call the application or execute its tests.
A member of Organization A requests a record owned by Organization B.
The selected API tests expect an unavailable response for cross-organization record IDs, including document downloads.
Review the response body and storage lookup as well as the status code; an error response must not contain the protected record.
Organization A attempts to change or remove Organization B’s customer.
The tests expect the request to fail and then retrieve the customer from its owning organization to check that its name is unchanged.
Extend the review to bulk updates, exports, and newly added endpoints.
A work order in Organization A refers to a site or technician in Organization B.
The selected cases expect invalid cross-organization assignments and linked records to be rejected.
Check every referenced object, even when the caller is authorized to create the parent record.
04 / TRACEABLE EVIDENCE
Selected source reviewed on November 6, 2026.
Source reviewed · tests not rerunapps/api/test/tenant-isolation.test.ts66c5f1ab5754These statements summarize the test definitions at this repository snapshot. They do not report a passing run, complete coverage, or an independent security audit. Application source stays private.
WHAT I WOULD EXAMINE NEXT
A fuller production review would trace organization context through queued jobs, inspect permissions for each role, and run the integration suite against an isolated test database.