Multi-Tenant Data
What must remain true about the business record when people edit, archive, export, or restore it? Attach tenant ownership to every protected record and enforce it centrally in queries and tests.
What You Will Be Able to Decide
- Explain multi-tenant data in product and business terms.
- Apply this decision: Attach tenant ownership to every protected record and enforce it centrally in queries and tests.
- Recognise this material risk: one customer can access another customer's records through an overlooked query or identifier.
- Use this review: Use one CRM contact and its related opportunity to test missing values, duplicate records, deletion, and restore.
A founder is deciding how the product should remember information and preserve its meaning over time. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
What must remain true about the business record when people edit, archive, export, or restore it? The course example is A lightweight CRM for a two-person sales team; use it to decide what evidence would justify the choice before a builder implements it.
What Does Multi-tenant Data Mean for Your Product?
A founder is deciding how the product should remember information and preserve its meaning over time.
Use the illustrative service for this course (A lightweight CRM for a two-person sales team) to make the choice concrete. What must remain true about the business record when people edit, archive, export, or restore it?
Technical term
Multi-Tenant Data
Multi-tenant data architecture stores information for multiple customers while preserving explicit ownership and isolation boundaries.
How Should a Founder Use Multi-tenant Data?
For a lightweight crm for a two-person sales team, ask what would happen if one customer can access another customer's records through an overlooked query or identifier.
For this decision, the useful standard is that the data model can represent the real business rules without ambiguity or silent corruption.
- Decision: Attach tenant ownership to every protected record and enforce it centrally in queries and tests.
- Evidence to request: show that the data model can represent the real business rules without ambiguity or silent corruption.
- Owner: name who will respond if one customer can access another customer's records through an overlooked query or identifier.
- Record the result in the data model and recovery plan.
- Practical review: Use one CRM contact and its related opportunity to test missing values, duplicate records, deletion, and restore.
How Do You Choose an Approach to Multi-tenant Data?
What must remain true about the business record when people edit, archive, export, or restore it? Attach tenant ownership to every protected record and enforce it centrally in queries and tests.
The risk is that one customer can access another customer's records through an overlooked query or identifier. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Multi-tenant Data?
What Warning Signs Should You Look For?
- The proposal does not address this risk: one customer can access another customer's records through an overlooked query or identifier.
- Nobody can show whether the data model can represent the real business rules without ambiguity or silent corruption.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to multi-tenant data?
- How have we reduced or accepted this risk: one customer can access another customer's records through an overlooked query or identifier.
- Can you demonstrate that the data model can represent the real business rules without ambiguity or silent corruption?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Attach tenant ownership to every protected record and enforce it centrally in queries and tests. Ask for evidence against the specific risk: one customer can access another customer's records through an overlooked query or identifier.