Map tenant ownership for case-management entities
The schema lists organization IDs on cases but not on comments or attachment relationships, leaving ownership implicit.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Relational modeling · Tenant boundaries
Estimated field mix
- Database engineering60%
- Security40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
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.
Setup prerequisites
- Create two synthetic organizations with overlapping display names.
- Use repository-level authorization and migration-backed constraints.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Identify the owning organization for every selected entity.
- List relationships that must stay within one organization.
- Separate truly global reference data from tenant data.
Implementation constraints
- Use a bounded case/project/comment schema.
Verification to include
- Trace ownership from a case attachment to its organization.
- Identify an intentionally ambiguous relationship and mark it unresolved.
Deliverables
- Tenant ownership map
Rollout and recovery
Review the map before migrations; keep ambiguous relationships out of new writes.
Value of the work
For the engineer: Practice tenant-aware keys, foreign keys and direct-write denial tests.
For the team: Review defense in depth for data isolation across ordinary and privileged writers.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.